Skip to main content
Glama

Aident AI

by ai.aident.loadout
OverviewDiscussionsAdmin

Check action readiness and cost

capabilities_preflight
Read-only

Validate an Action input, estimate its Aident credit cost, and return any per-Action approval requirement without executing it. Use this before dynamically priced or metered Actions when the cost depends on input.

Input Schema

NameRequiredDescriptionDefault
nameYesExact canonical Action name supplied directly or returned by capabilities_search or capabilities_get, for example "composio:reddit_tools:reddit_get_unread_inbox".
inputNoInput arguments to validate and price.
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.

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, for example \"composio:reddit_tools:reddit_get_unread_inbox\"."New value: +"Exact canonical Action name supplied directly or returned by capabilities_search or capabilities_get, for example \"composio:reddit_tools:reddit_get_unread_inbox\"."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior beyond that: it does not execute the Action, it estimates cost, and it surfaces per-Action approval requirements — details an agent needs for a preflight decision. No auth or rate-limit context is given, keeping it short of a 5.

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?

Two sentences, zero filler, and the core action plus its non-execution constraint are front-loaded. Every clause earns its place and no structured data is redundantly restated.

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?

With no output schema, the description usefully names the three things returned — validation result, credit cost estimate, and approval requirement — which is what an agent needs to interpret the call. It stops short of describing the return shape or what happens on invalid input, but coverage is solid for this tool's complexity.

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 name, input, context, and llm_model are all documented in the schema itself. The description adds only the framing that 'input' is what gets validated and priced, which is minimal value beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 states a specific verb+resource: validate an Action input, estimate its credit cost, and return approval requirements. It explicitly says 'without executing it', which cleanly separates it from the sibling capabilities_execute. An agent can identify this as a dry-run/preflight tool without opening either schema.

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

Usage Guidelines4/5

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

It gives a clear trigger condition: 'Use this before dynamically priced or metered Actions when the cost depends on input.' The 'without executing it' phrasing implicitly routes execution to capabilities_execute, but no alternative is named explicitly and no when-not case is spelled out (e.g. skip it for free/fixed-cost Actions).

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