Skip to main content
Glama

The evidence-backed control answer (paid)

get_control_evidence
Read-onlyIdempotent

The machine-readable, evidence-backed answer for one covered contract (the subject/v1 envelope): the full control graph (each Safe's signers, threshold, modules and guard, EIP-7702 delegates, and what is still unresolved), the complete state (every market, cap and queue), every pending change as a record with the transaction and log it rests on, the 20 most recent changes, and the value at stake. Use it when the user needs to verify or audit, not just read: the whole chain behind a role holder in one answer, what a pending change rests on, or the exact caps. Paid per call over x402; a call without a payment returns the price and where to buy, and charges nothing. get_control_state is the free summary.

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": "get_control_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe contract's address on Ethereum mainnet (0x and 40 hex digits), e.g. a Morpho vault's, a Safe's or a stablecoin's. Not a name: use search_covered_contracts to find an address.
sectionsNoOptional: only these parts of the envelope (default all). The whole answer can exceed 50 KB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses the payment mechanics (paid per call over x402) and, importantly, the failure mode: an unpaid call returns the price and where to buy and charges nothing. It also reveals scope limits ('what is still unresolved', 'the 20 most recent changes'), telling the agent the answer is bounded rather than exhaustive.

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

Conciseness4/5

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

The core purpose is front-loaded and each subsequent clause carries real information: contents, when-to-use, payment behavior, and the free alternative. The opening is a single very long sentence with a deep parenthetical list, which costs some scannability, but no sentence is filler.

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 must carry return-value semantics, and it does so thoroughly by describing each part of the envelope and flagging size (>50 KB, partly in schema) and unresolved items. The only gap is that it does not explain how the optional sections filter reshapes the answer, so an agent calling with sections set must reason from the schema alone.

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 both the address pattern and the sections enum, which sets the baseline at 3. The description's enumeration of answer components (control graph, state, records) loosely maps to the sections enum values and clarifies what 'one covered contract' scopes, but it never labels that mapping or explains how partial sections affect the response, so the added meaning is modest.

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 opens with a specific verb+resource ('the machine-readable, evidence-backed answer for one covered contract') and then enumerates exactly what that answer contains: control graph with signers/threshold/modules/guard/7702 delegates, full state with markets/caps/queues, pending changes with their transaction and log, the 20 most recent changes, and value at stake. It explicitly contrasts itself with the free sibling get_control_state, so an agent can separate the two without opening either schema.

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?

It states the selecting condition directly ('use it when the user needs to verify or audit, not just read') and gives three concrete trigger scenarios: tracing a role holder's whole chain, checking what a pending change rests on, and getting exact caps. It names the alternative ('get_control_state is the free summary'), making the free-vs-paid trade-off explicit rather than inferred.

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