describe_agent
Fleet-standard self-description.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
agent-offset-clearinghouse
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description only says 'self-description' but does not disclose read-only nature, side effects, or output characteristics. Behavioral traits are not communicated.
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?
The description is a single sentence, concise and to the point. However, 'Fleet-standard' is jargon that reduces clarity slightly; could be more straightforward.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and an output schema (unknown content), the description is minimally complete. It lacks context on what the output contains or how the tool fits in the broader system.
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?
No parameters exist, so baseline score of 4 applies. The description adds no parameter information, which is acceptable given zero parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Fleet-standard self-description' indicates the tool provides a description of itself, but 'Fleet-standard' is ambiguous and doesn't specify what aspects are described (e.g., capabilities, configuration). It is distinct from siblings but lacks specific verb or resource scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus siblings. The description does not mention alternatives or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool targets a distinct operation (e.g., book vs. list_credit vs. verra_supply; buy_offset vs. buy_offset_budget; certify_disbursement vs. verify_disbursement). No two tools have overlapping purposes, and descriptions clearly differentiate them.
Naming Consistency4/5
Most tools follow a verb_noun pattern (buy_offset, certify_disbursement, list_credits), but a few are noun phrases (book, disbursement_schedule, net_position, verra_supply). The naming is consistent in snake_case and readable, with only minor deviation from a pure verb-first style.
Tool Count5/5
19 tools cover the full domain of a carbon offset clearinghouse: credit listing, purchase, project registration, disbursement, settlement, verification, and Verra integration. Each tool serves a clear purpose without unnecessary redundancy.
Completeness4/5
The tool set provides full CRUD for core entities (e.g., list, buy, verify, delist credits; register and fund projects) plus advanced features (budget-based purchase, certification, settlement, Verra records). Minor gaps like a missing update for projects or credits are acceptable given the domain's constraints.