Skip to main content
Glama

What Ampdat Control covers

get_coverage
Read-onlyIdempotent

What this server can answer about: which contract families on which chain (today, on Ethereum mainnet: every Morpho vault, MetaMorpho v1.0 and v1.1 and Morpho Vaults V2; the Safes that hold those vaults' roles; and the contracts of six stablecoins, USDC, USDT, USDS, DAI, PYUSD and USD1), how many contracts, and the block the data is at. Call it once to learn the scope, or with address to check whether one address is covered before relying on an answer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoOptional: check this address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the data is currently Ethereum-mainnet-only, the scope enumerates specific vault versions and stablecoins, and the response includes a block height for freshness. The chain limitation is the key disclosure an agent needs before trusting downstream answers.

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

Conciseness3/5

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

The entire definition is one long, heavily parenthesized sentence that is hard to scan; the enumeration of vault versions and six stablecoin tickers is informative but bulky. The actionable guidance ('call it once... or with `address`') is buried at the end rather than 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 does the work of explaining what comes back: families per chain, contract counts, and the block height. For a zero-required-parameter scope tool this is close to complete; only the precise response shape of the `address` check result is left implicit.

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 the single optional parameter is documented as an address with a strict 0x-pattern. The description adds purpose to it (a coverage check before relying on an answer), which is helpful, but at one optional parameter with full schema coverage the baseline 3 is appropriate.

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 states concretely what the tool reports: which contract families on which chain, contract counts, and the block height the data is at, plus the exact scope currently covered (Morpho vaults, Safes holding roles, six stablecoins). It is clearly a scope/coverage tool rather than an evidence or state lookup, so it is distinguishable from the siblings, though no sibling is named explicitly.

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?

It gives two concrete call modes: call once to learn the scope, or pass `address` to verify a single address is covered before relying on an answer. That is real when-to-use guidance tied to a decision the agent must make. It stops short of naming alternatives (e.g. search_covered_contracts) for enumerating covered addresses.

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.

Resources