Moralis MCP Server

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 mentions accessing stats but doesn't disclose behavioral traits such as whether this is a read-only operation, potential rate limits, authentication requirements, data freshness, or what the output format looks like (e.g., JSON structure, pagination). This leaves significant gaps for an agent to understand how to interact with the tool effectively.

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

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

The description is concise and front-loaded, stating the core purpose in one sentence. There's no wasted text, but it could be slightly more informative without sacrificing brevity (e.g., by hinting at output structure). Overall, it's efficient and well-structured.

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

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

Given the complexity of accessing blockchain stats and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'category' means, how stats are grouped, what metrics are included, or the return format. For a tool with no structured output documentation, this leaves too much ambiguity for effective use.

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

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

The description adds minimal value beyond the input schema, which has 100% coverage. It mentions filtering by 'chain', but the schema already documents this parameter with a description and enum values. No additional semantics (e.g., default behavior, impact of not specifying chain) are provided, so the baseline score of 3 is appropriate given the schema does the heavy lifting.

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

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

The description clearly states the action ('Access') and the resource ('volume, buyers, sellers and transaction stats for a blockchain, grouped by category'), making the purpose specific. However, it doesn't explicitly differentiate from sibling tools like 'evm_getvolumestatsbychain' or 'evm_gettimeseriesvolumebycategory', which might offer similar functionality with different grouping or time-series aspects.

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

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

The description provides minimal guidance by mentioning filtering by 'chain', but it doesn't specify when to use this tool versus alternatives (e.g., 'evm_getvolumestatsbychain' for chain-level stats or 'evm_gettimeseriesvolumebycategory' for time-series data). No exclusions, prerequisites, or context for usage are provided.

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