Server Quality Checklist

Tool Scores

• get_sol_priceA
  3.7/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 tool's behavior as fetching a current price, implying it's a read-only operation with no destructive effects. However, it lacks details on data sources, rate limits, error handling, or response format, leaving gaps in behavioral context.

  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, efficient sentence that directly states the tool's function with no unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

  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?

  Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but minimal. It covers the basic purpose but lacks context on usage, behavioral traits like reliability or latency, and output details, which could be helpful for an agent.

  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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately adds no parameter details, focusing only on the tool's purpose. This meets the baseline for tools with no parameters.

  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 specific action ('Get') and resource ('current SOL/USD price'), with no ambiguity. It distinguishes itself from siblings like 'detect_dex', 'get_token_info', and 'scan_wallet' by focusing solely on price retrieval for a specific cryptocurrency pair.

  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?

  The description provides no guidance on when to use this tool versus alternatives. It does not mention scenarios where it's appropriate (e.g., real-time price checks) or when other tools might be better (e.g., using 'get_token_info' for broader token data).

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

• detect_dexA
  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 full burden. It discloses the return data (DEX name, pool address, token details, price, market cap, liquidity) and supported DEXs, which is useful behavioral context. However, it doesn't mention error handling, rate limits, authentication needs, or whether the operation is read-only/destructive.

  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 with zero waste: first states purpose and return values, second lists supported DEXs. Every element adds value, and it's front-loaded with the core functionality.

  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 1 parameter with full schema coverage, no annotations, and no output schema, the description is reasonably complete: it explains what the tool does, what it returns, and supported DEXs. However, for a tool returning financial data, it could better address accuracy, freshness, or limitations (e.g., 'and more' is vague).

  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 the mint parameter fully. The description adds no additional parameter semantics beyond what the schema provides (e.g., no examples or constraints on mint format beyond base58). Baseline 3 is appropriate when schema does the heavy lifting.

  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 specific action ('detect which DEX/AMM a Solana token trades on') and resource ('Solana token'), distinguishing it from siblings like get_sol_price (price only), get_token_info (general token data), and scan_wallet (wallet analysis). It explicitly lists supported DEXs, making the scope unambiguous.

  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 implies usage context (identifying trading venues for Solana tokens) but doesn't explicitly state when to use this tool versus alternatives like get_token_info. It mentions supported DEXs, which helps scope applicability, but lacks explicit exclusions or comparisons to 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_infoA
  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. It discloses the return format (name, symbol, image, USD price, DEX, market cap, liquidity) and the array limit (up to 10 mints), which are useful behavioral traits. However, it doesn't mention rate limits, authentication needs, error handling, or whether this is a read-only operation (though implied by 'Get').

  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 with zero waste. The first sentence states purpose and return values, the second specifies parameter handling. Every word contributes directly to tool understanding, and information is front-loaded appropriately.

  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 annotations and no output schema, the description provides good coverage: it explains what the tool does, what it returns, and parameter constraints. The main gap is lack of explicit behavioral context (e.g., rate limits, errors), but given the tool's apparent simplicity, this 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?

  Schema description coverage is 100%, so the schema already documents the 'mints' parameter thoroughly. The description adds marginal value by restating the array limit ('up to 10') and clarifying it can accept 'a single mint or array', but doesn't provide additional semantic context beyond what's in the schema. Baseline is 3, but the slight reinforcement earns a 4.

  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 action ('Get metadata and pricing'), the resource ('Solana tokens'), and the scope ('one or more'). It distinguishes from sibling tools like 'get_sol_price' (specific to SOL) and 'detect_dex' (different functionality). The verb+resource combination is specific and unambiguous.

  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 usage by specifying what it returns (metadata and pricing for Solana tokens), but doesn't explicitly state when to use it versus alternatives like 'get_sol_price' or 'detect_dex'. No guidance on prerequisites, error conditions, or when-not-to-use scenarios is provided.

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

• scan_walletA
  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 of behavioral disclosure. It effectively communicates key behavioral traits: the operation is free, read-only, doesn't require private keys, and returns specific metrics (count and estimated SOL). It doesn't mention rate limits, error conditions, or performance characteristics, but provides sufficient core information for a tool with one 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 perfectly concise and front-loaded. The first sentence establishes the core purpose, the second specifies the return values, and the third provides important usage context. Every sentence earns its place with zero 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?

  Given the tool's moderate complexity (single parameter, no output schema, no annotations), the description provides good completeness. It explains what the tool does, what it returns, and key behavioral constraints. The main gap is the lack of output schema, but the description adequately describes the return values (count and estimated SOL).

  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% description coverage, with the single parameter 'wallet' already documented as 'Solana wallet address (base58)' with length constraints. The description doesn't add any additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 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 the specific action ('Scan a Solana wallet'), target resource ('reclaimable SOL locked in empty token accounts'), and output ('Returns count of closeable accounts and estimated SOL recoverable'). It distinguishes itself from sibling tools by focusing on wallet scanning for reclaimable SOL rather than DEX detection, price checking, or token information retrieval.

  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 provides clear context for when to use this tool: to find reclaimable SOL in empty token accounts. It explicitly states 'Free, read-only — no private key needed,' which helps determine appropriate usage scenarios. However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the sibling tools.

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