Aident AI

capabilities_get

Read-only

Get full metadata for a capability by exact canonical name.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Exact capability name. For integration-backed Actions, pass a canonical name supplied directly or returned by capabilities_search unchanged, for example "composio:gmail_tools:gmail_send_email". Bare or legacy Action names are not accepted; migrate them to ${integration_type}:${integration_name}:${action_name}.
`parts`	No	Specific parts to include (all if omitted). Use sourceCode for capability source.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`type`	Yes
`riskLevel`	No
`sourceCode`	No
`description`	No
`inputSchema`	No
`outputSchema`	No
`userAccounts`	No
`operationType`	No
`pricingSummary`	No
`executionBackend`	No
`requiredBundleId`	No
`platformAuthEnabled`	No
`requiredIntegrations`	Yes
`minimumAbilityVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "context",
+  "llm_model"
+]

Changed2 schema fields changedSep 9, 2026

changedInput schema / properties / name / description

Previous value: -"Exact capability name. For integration-backed Actions, pass the canonical name returned by capabilities_search unchanged, for example \"composio:gmail_tools:gmail_send_email\". Bare or legacy Action names are not accepted; migrate them to ${integration_type}:${integration_name}:${action_name}."New value: +"Exact capability name. For integration-backed Actions, pass a canonical name supplied directly or returned by capabilities_search unchanged, for example \"composio:gmail_tools:gmail_send_email\". Bare or legacy Action names are not accepted; migrate them to ${integration_type}:${integration_name}:${action_name}."

addedOutput schema / properties / platformAuthEnabled
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedSep 7, 2026

addedOutput schema / properties / pricingSummary / properties / policy

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "chargeTiming": {
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "family": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "settlementSource": {
+      "type": "string"
+    },
+    "version": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "version",
+    "family",
+    "description",
+    "chargeTiming",
+    "settlementSource"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "name",
-  "description",
-  "type",
-  "requiredIntegrations"
-]New value: +[
+  "name",
+  "type",
+  "requiredIntegrations"
+]

Changed1 schema field changedAug 14, 2026

addedOutput schema / properties / userAccounts

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "alias": {
+        "type": "string"
+      },
+      "createdAt": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "isDefault": {
+        "type": "boolean"
+      },
+      "lastUsedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "status": {
+        "enum": [
+          "active",
+          "expired"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "alias",
+      "isDefault",
+      "createdAt",
+      "lastUsedAt",
+      "status"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedAug 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "description": {
+      "type": "string"
+    },
+    "executionBackend": {
+      "type": "string"
+    },
+    "inputSchema": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "minimumAbilityVersion": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "operationType": {
+      "enum": [
+        "read",
+        "write"
+      ],
+      "type": "string"
+    },
+    "outputSchema": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "pricingSummary": {
+      "additionalProperties": false,
+      "properties": {
+        "label": {
+          "type": "string"
+        },
+        "maxCreditsPerCall": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "minCreditsPerCall": {
+          "minimum": 0,
+          "type": "number"
+        },
+        "type": {
+          "enum": [
+            "flat_rate",
+            "dynamic",
+            "mixed"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "type",
+        "label"
+      ],
+      "type": "object"
+    },
+    "requiredBundleId": {
+      "type": "string"
+    },
+    "requiredIntegrations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "riskLevel": {
+      "maximum": 5,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "sourceCode": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "name",
+    "description",
+    "type",
+    "requiredIntegrations"
+  ],
+  "type": "object"
+}

First observedAug 7, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is covered. The description adds little beyond 'full metadata' and 'exact canonical name'; it does not disclose error behavior, partial-failure modes, or the significance of the parts parameter. This is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that states the resource, verb, and precondition with no filler. Every word contributes to understanding the tool's core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema and 100% schema coverage, so the one-line description does not need to explain return values or parameter details. It is complete enough for correct invocation, though it relies on the schema for required analytics-parameter context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters thoroughly, including canonical-name migration rules and the required analytics fields. The description's reference to 'exact canonical name' adds marginal emphasis but mostly duplicates the schema's first sentence.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Get full metadata for a capability') and adds the key qualifier 'by exact canonical name,' which distinguishes it from siblings like capabilities_search (fuzzy lookup) and capabilities_execute (invocation). An agent can tell what this tool does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by exact canonical name' implies the tool is for when the caller already knows the exact identifier, but the description never names capabilities_search as the alternative for finding capabilities or capabilities_execute for running them. Usage context is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Aident AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?