Skip to main content
Glama

Aident AI

by ai.aident.loadout
OverviewDiscussionsAdmin

Run an action through Aident

capabilities_execute
Destructive

Execute a capability by exact name. Copy canonical Action names supplied directly or returned by capabilities_search or capabilities_get without modification; Actions may use integration or Sandbox-local execution backends, while Skill names use the Skill runtime. For requires-user-acknowledgement, show the effect and redacted inputs, ask the user, then retry the identical request with acknowledgementScope set to an available scope. For credit-approval-required, ask the user and retry once with the returned approvalToken. Before a side-effecting Action, call capabilities_get first: when it returns more than one active entry in userAccounts, surface the default alias and pass an explicit accountAlias whenever the user wants a non-default account; an omitted alias routes through the active default account, and the server rejects an omitted alias with account-selection-required only when no active default exists. Skill execution never accepts accountAlias.

Input Schema

NameRequiredDescriptionDefault
nameYesExact canonical Action name supplied directly or returned by capabilities_search or capabilities_get (e.g. "composio:reddit_tools:reddit_get_unread_inbox"). Actions may use integration or Sandbox-local execution backends. Do not use raw artifact names or dotted aliases.
inputNoInput arguments matching the capability schema
contextYesExplain 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_modelYesThe 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.
timeoutSecNoMaximum hosted CLI runtime in seconds. Capped by the Action resource limit and the synchronous request budget.
accountAliasNoExact account alias from capabilities_get userAccounts for Actions whose Integration has multiple accounts. Requires the multi-account feature; omit for default routing.
approvalTokenNoOne-time credit approval token returned in creditApproval.approvalToken by capabilities_preflight or credit-approval-required. Not used for Action risk acknowledgement.
acknowledgementScopeNoAfter requires-user-acknowledgement and explicit user approval, retry the identical Action and input with a scope listed in availableScopes (once, session, always).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Exact canonical Action name returned by capabilities_search or capabilities_get (e.g. \"composio:reddit_tools:reddit_get_unread_inbox\"). Actions may use integration or Sandbox-local execution backends. Do not use raw artifact names or dotted aliases."New value: +"Exact canonical Action name supplied directly or returned by capabilities_search or capabilities_get (e.g. \"composio:reddit_tools:reddit_get_unread_inbox\"). Actions may use integration or Sandbox-local execution backends. Do not use raw artifact names or dotted aliases."
  3. Changed1 schema field changed
    • addedInput schema / properties / accountAlias
      Added value: +{
+  "description": "Exact account alias from capabilities_get userAccounts for Actions whose Integration has multiple accounts. Requires the multi-account feature; omit for default routing.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. Changed2 schema fields changed
    • addedInput schema / properties / acknowledgementScope
      Added value: +{
+  "description": "After requires-user-acknowledgement and explicit user approval, retry the identical Action and input with a scope listed in availableScopes (once, session, always).",
+  "enum": [
+    "once",
+    "session",
+    "always"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / approvalToken / description
      Previous value: -"One-time approval token returned by capabilities_preflight or a blocked execution."New value: +"One-time credit approval token returned in creditApproval.approvalToken by capabilities_preflight or credit-approval-required. Not used for Action risk acknowledgement."
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description goes well beyond that: it discloses the acknowledgement handshake, the credit-approval retry protocol, the exact server error (account-selection-required) triggered by an omitted alias when no default exists, and the rule that Skill execution never accepts accountAlias. This is substantive behavioral context not present in structured fields.

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

Conciseness4/5

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

Front-loaded with the core action and dense with actionable rules, with no filler sentences. It is long, but nearly every clause maps to a distinct execution rule (name fidelity, backends, ack, approval, account routing), so length is largely earned.

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

Completeness5/5

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

For an 8-parameter destructive, open-world executor with a nested input object and no output schema, the description covers the risky flows (acknowledgement, credit approval, account selection) that an agent most needs to invoke it correctly. Return values are not described, but no output schema exists and little return-form detail is required to call it.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real routing meaning beyond the schema: it explains that an omitted accountAlias routes through the active default and is only rejected when no default exists, and that acknowledgementScope and approvalToken are meant for a retry of the identical request. These are semantics the schema fields do not spell out.

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?

States a specific verb and resource ('Execute a capability by exact name') and immediately distinguishes itself from the retrieval siblings capabilities_search and capabilities_get by framing them as name sources rather than executors. 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 Guidelines5/5

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

Explicit routing rules: call capabilities_get before a side-effecting Action, retry with acknowledgementScope for requires-user-acknowledgement, retry once with approvalToken for credit-approval-required, and when to set accountAlias. Alternatives and prerequisites are named rather than implied.

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

All Aident AI toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources