Skip to main content
Glama

Who controls this contract, and what is pending

get_control_state
Read-onlyIdempotent

Who controls a covered contract right now: who holds each role and what that holder is (a single key, a Safe and its threshold, a DAO, a known contract); what each role can change and how much notice (timelock) each change gives; and every change already queued, when it can take effect and who can revoke it. For a Morpho vault, before a deposit or while holding: the owner, curator, guardian or sentinels, and allocators. For a stablecoin: who can mint, burn, pause, freeze, upgrade the contract or appoint those roles. For a Safe: its signers' threshold, modules and guards, and the vault roles it holds (holds_roles_on); a Safe changes in one transaction, so nothing in it is pending. Deterministic facts from the chain at a stated block; a title search, not a rating, so it returns no safety score. An address that is not covered returns covered: false.

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_state"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered; the description adds genuinely non-obvious behavior: results are deterministic chain facts pinned to a stated block, and uncovered addresses return covered: false rather than erroring. It also explains a semantic edge case for Safes (atomic change, so nothing is pending).

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 answer is front-loaded and the per-contract-type examples are compactly parallel, so a reader can stop after the first sentence. The 'title search, not a rating' aside is useful framing but slightly editorial, keeping it just below maximal conciseness.

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?

There is no output schema, and the description compensates fully by describing the shape of the return (roles, holder identity, change powers, timelock notice, queued changes with effective time and revoker) and the covered:false sentinel. For a single-address read tool this leaves no significant unknown before calling.

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?

With a single parameter at 100% schema coverage (pattern, mainnet constraint, examples, and the search_covered_contracts pointer), the schema already carries the load. The description reinforces which address classes are valid but adds no new format or validation detail beyond the schema.

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 opening clause gives a specific verb and resource ('Who controls a covered contract right now'), then enumerates the exact payload: role holders, holder type (single key, Safe + threshold, DAO, known contract), per-role powers and timelock notice, and queued changes. It is further concretized per contract class (Morpho vault, stablecoin, Safe), so an agent can tell exactly what this returns and how it differs from an evidence or change-record lookup.

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 states concrete usage occasions ('before a deposit or while holding' a Morpho vault) and a clear negative scope ('a title search, not a rating, so it returns no safety score'), plus a routing rule away from a sibling when the input is a name rather than an address. What it lacks is any explicit distinction from the closely named get_control_evidence and get_change_records, which an agent must guess between.

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