Skip to main content
Glama

Find a covered contract by name

search_covered_contracts
Read-onlyIdempotent

Find a covered contract's address from words the user gave: its name (e.g. 'Steakhouse USDC'), its asset symbol (e.g. 'WETH') or part of its address. Returns up to limit matches with address, name, asset and family. Use it when the user names a vault or a coin instead of giving an address, then call get_control_state with the address.

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": {
      "query": "<query>"
    },
    "name": "search_covered_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords that must all appear in the contract's name, asset symbol, family or address. Case does not matter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the return shape ('up to `limit` matches with address, name, asset and family') and the multi-match/ambiguity behavior, which matters because no output schema exists. It does not mention the maximum of 25 or what happens when zero matches are found.

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, front-loaded with what the tool does and the accepted inputs, then the usage rule and the handoff. No filler or restated title.

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?

For a two-parameter lookup tool with no output schema, the description covers input forms, return fields, result-count behavior and the next tool to call. An agent has everything it needs to invoke it correctly without opening the schema.

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 50% — `query` is documented but `limit` has only a default and bounds in the schema. The description compensates by explaining that `limit` caps the number of returned matches, and reinforces that query words must all match across name, symbol or address. It stops short of explaining matching/all-token semantics for multi-word queries.

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?

Specific verb plus resource: 'Find a covered contract's address from words the user gave', with concrete examples of the accepted word types (name 'Steakhouse USDC', symbol 'WETH', partial address). It is clearly distinguishable from the get_control_state / get_change_records / get_coverage siblings, which take or return on-chain data rather than performing name resolution.

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

Usage Guidelines5/5

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

Explicit trigger condition ('when the user names a vault or a coin instead of giving an address') and an explicit follow-up ('then call get_control_state with the address'), which chains the two tools rather than leaving the agent to infer the sequence.

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