Tool Type Generator | Composio Docs

This is a bit of a checky tutorial as it is dogfooding the docs tool generation process.

To motivate this example clearly, in our tools section — we have details about let’s say Github tool, that shows its auth scheme, actions and their params.

Now why would anyone outside of Composio want to do this? Well if you are building a platform on top of Composio, perchance a Workflow builder like langflow. You would want to show some or all of this information to your users.

This is a non standard use case, that we support and love users building on top of us but if this is uninteresting to you, you can skip this tutorial.

How does one build a tool type generator?

In composio, we have two internal states for tools

Raw tool definition
Provider tool definition

The raw tool definition is an generic input output schema definition that we internally for tools, we expose it for customers if they want to build on top of it but it is not the primary way tools are normally used.

The provider tool definition, translates this raw tool definition to the specific schema of a provider (by default openai).

For building something like this, we need to use the raw tool definition.

Getting the raw tool definition

Of course, you need to initiate the Composio sdk first and use a COMPOSIO_API_KEY environment variable.

tool_doc_generator/main.py

1         if "properties" in params:
2             properties = params.get("properties", {})

Let us see an example output for a raw GMAIL toolkit, with all of its tools.

this is just a taste but you can see the full output here.

output.json

1 [
2     {
3         "deprecated": {
4             "available_versions": [
5                 "0_1",
6                 "latest",
7                 "latest:base"
8             ],
9             "display_name": "Modify email labels",
10             "is_deprecated": false,
11             "toolkit": {
12                 "logo": "https://cdn.jsdelivr.net/gh/ComposioHQ/open-logos@master/gmail.svg"
13             },
14             "version": "0_1",
15             "displayName": "Modify email labels"
16         },
17         "description": "Adds and/or removes specified gmail labels for a message; ensure `message id` and all `label ids` are valid (use 'listlabels' for custom label ids).",
18         "input_parameters": {
19             "properties": {
20                 "add_label_ids": {
21                     "default": [],
22                     "description": "Label IDs to add. For custom labels, obtain IDs via 'listLabels'. System labels (e.g., 'INBOX', 'SPAM') can also be used.",
23                     "examples": [
24                         "STARRED",
25                         "IMPORTANT",
26                         "Label_123"
27                     ],
28                     "items": {
29                         "type": "string"
30                     },
31                     "title": "Add Label Ids",
32                     "type": "array"
33                 },
34                 "message_id": {
35                     "description": "Immutable ID of the message to modify (e.g., from 'fetchEmails' or 'fetchMessagesByThreadId').",
36                     "examples": [
37                         "17f1b2b9c1b2a3d4"
38                     ],
39                     "title": "Message Id",
40                     "type": "string"
41                 },
42                 "remove_label_ids": {
43                     "default": [],
44                     "description": "Label IDs to remove. For custom labels, obtain IDs via 'listLabels'. System labels can also be used.",
45                     "examples": [
46                         "UNREAD",
47                         "Label_456"
48                     ],
49                     "items": {
50                         "type": "string"
51                     },
52                     "title": "Remove Label Ids",
53                     "type": "array"
54                 },
55                 "user_id": {
56                     "default": "me",
57                     "description": "User's email address or 'me' for the authenticated user.",
58                     "examples": [
59                         "me",
60                         "user@example.com"
61                     ],
62                     "title": "User Id",
63                     "type": "string"
64                 }
65             },
66             "required": [
67                 "message_id"
68             ],
69             "title": "AddLabelToEmailRequest",
70             "type": "object"
71         },
72         "name": "Modify email labels",
73         "no_auth": false,
74         "output_parameters": {
75             "properties": {
76                 "data": {
77                     "description": "Data from the action execution",
78                     "properties": {
79                         "response_data": {
80                             "description": "Full `Message` resource with updated labels.",
81                             "title": "Response Data",
82                             "type": "object"
83                         }
84                     },
85                     "required": [
86                         "response_data"
87                     ],
88                     "title": "Data",
89                     "type": "object"
90                 },
91                 "error": {
92                     "anyOf": [
93                         {
94                             "type": "string"
95                         },
96                         {
97                             "type": "null"
98                         }
99                     ],
100                     "default": null,

1 jq '.[0] | keys' pages/src/examples/tool-generator/output.json
2 [
3   "available_versions",
4   "deprecated",
5   "description",
6   "input_parameters",
7   "name",
8   "no_auth",
9   "output_parameters",
10   "scopes",
11   "slug",
12   "tags",
13   "toolkit",
14   "version"
15 ]

There is a bunch of useful information here, around the input_parameters and output_parameters for this example but scopes is very valuable to know what permissions are required for this tool.

Now from these input_parameters and output_parameters you can showcase the tool definitions.

tool_doc_generator/main.py

1         fields = []
2         _, field_config = field
3 
4         for field_list, required in [
5             (getattr(field_config, "required", []), True),
6             (getattr(field_config, "optional", []), False),
7         ]:
8             for f in field_list:
9                 if hasattr(f, "name"):
10                     fields.append(self._create_param_from_field(f, required))

There is a bunch of other processing things happening here that are super generally relevant, so not going to call them out here that said there is another thing i want to showcase

Toolkit Information

Toolkis are what we call apps or integrations, for us they are a collection of tools. GMAIL has GMAIL_SEND_EMAIL as a tool.

Now for building something out like this, you might also want information about the toolkit itself.

A toolkit has information like categories or auth_schemes

tool_doc_generator/main.py

1             properties = params.get("properties", {})
2             required = params.get("required", [])
3 
4             for name, schema in properties.items():

auth_schemes here are OAUTH2, API_KEY or BASIC_AUTH, etc — essentially the types of how one could authenticate with the toolkit.

tool_doc_generator/main.py

1                         default=schema.get("default", ""),
2                         required=name in required,
3                     )
4                 )
5         else:
6             for name, schema in params.items():
7                 if isinstance(schema, dict):
8                     param_list.append(
9                         MDX.as_param(
10                             name=name,

Here is a way to parse the auth_scheme data

these are tuple objects as they have different schema for specific conditions like auth_config_creation or connected_account_initiation

they also have required and optional fields.

the context here is there are some fields you need while creating an auth config and some you need while connecting an account. this separation is done by the tuple here

tool_doc_generator/main.py

1         auth_schemes: t.Optional[t.List[toolkit_retrieve_response.AuthConfigDetail]] = None,
2     ) -> None:
3         schemes = ", ".join(
4             self._get_auth_type(s) for s in (auth_schemes or []) if self._extract_auth_fields(s)
5         )
6         self._blocks.extend(
7             [
8                 f"""## Connecting to {app_name}
9 ### Create an auth config
10 Use the dashboard to create an auth config for the {app_name} toolkit. This allows you to connect multiple {app_name} accounts to Composio for agents to use.
11 
12 <Steps>
13   <Step title="Select App">
14     Navigate to **[{app_name}](https://platform.composio.dev?next_page=/marketplace/{app_name})**.
15   </Step>
16   <Step title="Configure Auth Config Settings">
17     Select among the supported auth schemes of and configure them here.
18   </Step>
19   <Step title="Create and Get auth config ID">
20     Click **"Create {app_name} Auth Config"**. After creation, **copy the displayed ID starting with `ac_`**. This is your auth config ID. This is _not_ a sensitive ID -- you can save it in environment variables or a database.
21     **This ID will be used to create connections to the toolkit for a given user.**
22   </Step>
23 </Steps>
24 """
25             ],
26         )
27 
28         # Add auth code snippets
29         self._add_auth_section(app_name, app_slug, auth_schemes)
30 
31     def _add_auth_section(
32         self,
33         app_name: str,
34         app_slug: str,
35         auth_schemes: t.List[toolkit_retrieve_response.AuthConfigDetail] = None,
36     ) -> None:
37         """Add code snippets for each auth scheme using direct template processing"""
38         if not auth_schemes:
39             return
40         
41         self._blocks.append("### Connect Your Account")
42         
43         # Group auth schemes by type to avoid duplicates
44         seen_auth_types = set()
45

This is a fairly minimal explanation for the amount of code, as most of it is not super related to composio but it will be a good example on seeing behind the scenes of how composio is working and how to leverage the platform further.