Server Quality Checklist

Tool Scores

• chain_tvlA
  3.9/5.0
  Behavior3/5

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

  With no annotations, the description carries the full burden for behavioral disclosure. It adds useful context (data source DefiLlama, categories like DEX venues and RWA subset), but it does not explicitly state whether this is a read-only operation, nor does it mention return format, latency, or other behavioral traits. This is adequate for a simple data-retrieval tool but not comprehensive.

  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 two concise sentences that pack in the data source, the specific output components, and the intended use cases. Every clause adds value, with no fluff or repetition.

  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?

  There is no output schema, so the description should explain what the tool returns. It does list the output components (TVL, protocols, DEX venues, RWA subset) and provides use-case guidance. It could be more explicit about whether the data is a snapshot or includes historical trends, but the 1d/7d change hints at time-lapse. Overall, it is complete enough for a zero-parameter tool.

  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?

  There are zero parameters, so the schema coverage is 100% by default. The description correctly avoids inventing parameter details. Per calibration, a baseline of 4 applies to zero-parameter tools, and the description adds no unnecessary parameter information.

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

  Purpose4/5

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

  The description clearly states what the tool provides: total TVL, largest protocols with 1d/7d change, DEX venues, and RWA subset on Robinhood Chain. It lacks an explicit verb like 'get' or 'list', but the resource and scope are unambiguous, distinguishing it from sibling tools that cover markets, tokens, and agents.

  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?

  The description explicitly says 'Use for market structure, venue depth, and trend analysis,' providing clear contexts for use. However, it doesn't mention when not to use it or name specific alternatives, so it falls short of a 5.

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

• get_agent_statusA
  4/5.0
  Behavior3/5

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

  With no annotations, the description carries the burden of behavioral disclosure. It implies a read-only status check and lists the returned data, but it does not explicitly state that there are no side effects or describe error/edge-case behavior. The ATLAS_API_URL requirement is a useful context, but safety is only implied.

  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 purpose first and then lists key details. There is no filler; every phrase contributes meaningful information.

  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?

  Since there is no output schema, the description takes on the job of explaining return values by naming five categories of status data. It does not fully describe the response structure or possible error conditions, but for a simple status tool it is reasonably complete.

  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?

  The schema has zero parameters, so there are no property descriptions to rely on. The description adds value by mentioning a non-parameter configuration requirement (ATLAS_API_URL) and describing the content of the status report. This meets the baseline for zero-parameter tools.

  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 starts with 'Status of the ATLAS research agent' which clearly identifies both the resource and the action. It enumerates specific fields (model, chain configuration, publish interval, atlas count, memory stats) making it distinct from all sibling tools that focus on markets or tokens.

  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 description provides a prerequisite ('Requires ATLAS_API_URL') but no explicit guidance on when to use this tool versus alternatives. The context is implied by the tool name and the fact it is the only agent-status tool among siblings.

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

• get_token_holdersA
  4/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the full burden. It discloses the data source (Blockscout index) and input flexibility (ticker or contract address), but does not explicitly mention safety profile, side effects, or error behavior. For a simple read-only query, 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 two sentences, immediately states what the tool returns, and avoids any filler. It is front-loaded and every sentence earns its place.

  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?

  Given the tool's low complexity (one parameter, no output schema), the description is nearly complete. It specifies the key outputs (holder count and top-10 concentration), data source, and input. It omits potential limitations or error cases, but for a simple query tool this is sufficient.

  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?

  The schema already provides 100% coverage of the single parameter 'token' with a clear description ('Ticker or ERC-20 contract address (0x...)'). The description reinforces this but adds no new meaning beyond what the schema offers, so the baseline of 3 is appropriate.

  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 clearly states the tool's function: it returns holder count and top-10 holder concentration for an ERC-20 on Robinhood Chain. This specific verb-resource pairing distinguishes it from sibling tools like get_token_supply or get_token_market, which focus on different data aspects.

  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?

  The description explicitly says to use it for analyzing how concentrated ownership of a tokenized asset is, which provides clear context. It does not name alternative tools or state when not to use it, but the intended use case is well implied.

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

• get_token_marketA
  4/5.0
  Behavior3/5

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

  No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals the data source (GeckoTerminal) and implicitly frames this as a read-only 'view', but does not explicitly state safety, error behavior, rate limits, or permissions. This is moderate transparency for a simple market lookup.

  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 two sentences long, front-loaded with the core purpose and output list, followed by input guidance. Every sentence contributes relevant information with no redundancy.

  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?

  For a single-parameter tool with no output schema, the description provides the key return fields and input formats. It omits explicit response formatting and failure cases, but still gives an agent enough context to invoke the tool correctly.

  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?

  Although the schema already covers the 'token' parameter with 100% completeness, the description adds valuable nuance by explaining that a ticker like 'TSLA' resolves to 'TSLAx', a behavior not mentioned in the schema. It also confirms both accepted input types.

  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 clearly states the tool's purpose: retrieving a market view of a tokenized stock with specific data fields (price, 1h/24h change, market cap, pool liquidity, 24h volume) via GeckoTerminal. This distinguishes it from siblings like list_markets and get_token_supply by focusing on a single token's market metrics.

  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 description implies when to use this tool (for market data of a specific token) and explains acceptable inputs (ticker or contract address), but it does not explicitly contrast with sibling tools or state when not to use it. No alternatives or exclusions are mentioned.

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

• list_marketsA
  4/5.0
  Behavior3/5

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

  With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the data source (chain trading pools), return fields, and classification methodology. However, it does not mention caching behavior, potential latency, or explicitly state that it is a read-only operation, though these are somewhat implied and partially covered by the schema's refresh parameter.

  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 two sentences, front-loaded with the core purpose, and every sentence adds value: source, return fields, and usage priority. No wasted words.

  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?

  For a low-complexity list tool with 2 well-described parameters and no output schema, the description adequately covers return values and purpose. It could mention result limits or pagination, but given the simple nature and schema coverage, it is sufficiently complete.

  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?

  The input schema has 100% coverage with both parameters (refresh and includeNonEquity) fully described. The description adds no parameter-specific meaning but also does not need to, as the schema already provides clear semantics. This aligns with the baseline for high schema coverage.

  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 clearly states what the tool does: lists tokenized stocks on Robinhood Chain, discovered from trading pools. It specifies the returned fields (ticker, contract address, liquidity, and equity classification logic), and positions itself as the entry point for research. This distinguishes it from sibling tools that focus on individual token details.

  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?

  The description explicitly says 'Call this first to learn what is available to research', providing clear when-to-use guidance. It does not explicitly name alternatives or when not to use, but the 'first' instruction strongly implies a discovery role before using more specific token tools.

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

• get_observation_historyA
  4.2/5.0
  Behavior3/5

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

  With no annotations, the description bears the burden. It discloses a prerequisite ('Requires ATLAS_API_URL') and explains key types. However, it does not explicitly state the operation is read-only, describe error behavior, or mention rate limits or pagination beyond the limit parameter.

  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 three sentences long, with no redundant information. The first sentence states purpose, the second explains key types, and the third gives the environment requirement. Every sentence adds value.

  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 could specify the response structure, but 'time series' implies a sequence of snapshots. The tool has few parameters and no annotations, and the description covers purpose, key semantics, and environment needs, making it reasonably complete.

  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?

  The schema already covers both parameters, but the description adds valuable examples ('TSLA' for price snapshots, 'chain-tvl', contract address for supply/holders), enriching the key parameter semantics beyond the schema's brief description.

  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 clearly identifies the tool as providing 'The ATLAS agent's recorded observation time series' with a specific use case ('trend detection and day-over-day comparison'). This distinguishes it from sibling tools that focus on current market data, token supply, holders, and TVL.

  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?

  The description states the tool is for 'trend detection and day-over-day comparison', giving clear context for when to use it. It does not explicitly name alternatives or exclusions, but the purpose statement implicitly differentiates it from sibling tools.

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

• get_token_supplyA
  4.2/5.0
  Behavior4/5

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

  With no annotations, the description carries the burden and does well by noting the tool reads 'directly from Robinhood Chain JSON-RPC at the current block,' implying a live, authoritative read rather than a cached value. It also labels itself as 'Source of truth,' setting expectations for accuracy.

  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?

  Three succinct sentences each serve a purpose: the first states the core function and data source, the second gives a concrete use case, and the third clarifies the accepted input. No wasted words.

  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?

  For a simple single-parameter read tool, the description covers what it does, when to use it, and what input is expected. It does not explicitly describe the return format or error behavior, but given the simplicity and absence of an output schema, this is adequate.

  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 coverage is 100% since the token property is described as 'Ticker or ERC-20 contract address (0x...)' and the description repeats this nearly verbatim. It adds minimal extra meaning beyond the schema, so baseline 3 applies.

  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?

  Clearly states the tool reads an ERC-20's total supply directly from Robinhood Chain JSON-RPC at the current block. This specific verb-resource combination differentiates it from siblings like get_token_holders or get_token_market.

  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?

  Explicitly provides a use case: 'Use to verify issuance and redemption of a tokenized stock.' However, it does not explicitly mention when not to use it or name alternative tools for similar tasks, so it stops short of a full 5.

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

• verify_token_contractA
  4.2/5.0
  Behavior4/5

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

  With no annotations provided, the description carries the full burden. It clearly discloses what the tool checks and returns (bytecode presence, name/symbol/decimals, block, chain ID), implying a read-only non-destructive operation. It doesn't mention error cases or response format, but for a verification tool this is reasonable disclosure.

  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 two sentences, front-loaded with purpose and output details, followed by a clear usage directive. Every sentence earns its place with no redundancy or filler.

  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?

  For a single-parameter read-only verification tool, the description covers the essential aspects: what the tool does, the inputs it accepts, the outputs it reports, and when to use it. It doesn't specify the return format, which could be inferred from the listed items, and there is no output schema. Given the tool's simplicity, this is sufficiently complete.

  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?

  The schema already provides a complete parameter description ('Ticker or ERC-20 contract address (0x...)'), so schema coverage is 100%. The description adds context about verification but offers no additional parameter-specific semantics beyond what the schema states, aligning with the baseline score of 3.

  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 clearly states the tool's function: verifying an ERC-20 contract on Robinhood Chain. It lists the specific checks performed (bytecode deployment, on-chain name/symbol/decimals, current block, chain ID), which distinguishes it from sibling tools focused on market data, supply, holders, and TVL.

  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?

  The phrase 'Use before trusting a market quote' provides explicit guidance on when this tool should be invoked. It doesn't explicitly state when not to use it or name alternatives, but the context is clear and actionable.

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

• list_research_atlasesA
  4.3/5.0
  Behavior4/5

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

  No annotations exist, so the description carries the full burden. It discloses ordering (newest first), frequency (one per cycle), content structure (conclusion, changes, evidence), and a setup requirement (ATLAS_API_URL). It doesn't explicitly state read-only nature or rate limits, but for a listing operation this is reasonably transparent.

  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 well-structured sentences: first defines the tool's output and ordering, second details item contents and requirement. No filler or repetition.

  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?

  Despite no output schema, the description explains what each atlas contains and the ordering. Combined with the optional limit parameter in the schema, it fully covers the tool's behavior for an agent to invoke it correctly.

  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?

  The only parameter, 'limit', is fully described in the schema with default and range. The description adds no additional parameter semantics, so baseline 3.

  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 clearly identifies the resource (research atlases), defines their nature (autonomous analyses of tokenized stocks and RWA ecosystem), and differentiates from sibling market/token tools by focusing on research outputs. The verb is implicit but obvious from the name and context.

  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?

  The description establishes clear context for when to use it: to retrieve ATLAS agent's published research atlases. It doesn't explicitly name alternatives or exclusions, but the niche is unambiguous given sibling tools are market data, so clear context without exclusions.

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