Skip to main content
Glama

contract_docs

Read-onlyIdempotent

Generate documentation for any verified EVM smart contract. Returns function descriptions, risk flags, interaction patterns, and security posture. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "contract_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum
addressYesContract address
focusFunctionsNoSpecific functions to document

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely non-obvious behavior: a 10-calls-per-day free quota and, critically, that exceeding it changes the response into a pay-per-call x402 endpoint with a price rather than docs. That altered-return behavior is exactly the kind of disclosure an agent cannot get from structured fields.

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 tight sentences: purpose first, return contents second, quota/fallback behavior last. No filler, and the most decision-relevant constraint is front-loaded.

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 enumerates return contents and covers the quota-degraded path. The only minor gap is whether the daily quota is per-key or global, but nothing an agent needs to invoke the tool correctly is missing.

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% and all three parameters (chain with enum, address, focusFunctions) are documented in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies.

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 names a specific verb (generate documentation) and resource (verified EVM smart contract), and enumerates the output content (function descriptions, risk flags, interaction patterns, security posture). This clearly separates it from monitoring or risk-scoring siblings, though it never names an alternative tool explicitly.

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 'verified EVM smart contract' qualifier implies when the tool applies and the quota line hints at volume limits, but there is no explicit when-to-use/when-not guidance and no routing to sibling tools such as risk_batch or contract_monitor for overlapping needs.

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.