Skip to main content
Glama

BRAINIAC Crypto Governance

Diff governance execution

crypto-governance_governance-execution-diff

Compare the structured actions in a caller-supplied DAO proposal with the caller-supplied execution calls. Targets, selectors, decoded parameters, and native value are compared. execution_match is exact, partial, mismatch, or indeterminate. risk_level is low, medium, high, or critical. The proposal description is not treated as the approved action list. No chain is queried, and approval or execution is not inferred from chain state. Price $0.05 USDC. POST /api/v1/crypto-governance/governance-execution-diff. Unpaid calls return 402 and do not run.

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": {
      "proposal": "<proposal>",
      "approvedActions": "<approvedActions>",
      "execution": "<execution>"
    },
    "name": "crypto-governance_governance-execution-diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
abiNo
chainIdNo
proposalYes
executionYes
fieldMappingNo
orderSensitiveNo
approvedActionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does well on the big points (no chain queried, chain state never used to infer approval/execution, proposal description explicitly NOT the approved action list, 402 when unpaid and the call does not run, $0.05 price). Gaps remain: what makes a result 'indeterminate', the meaning of orderSensitive, and how fieldMapping remaps fields are all undisclosed behavioral levers.

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?

Dense and front-loaded: the comparison and its scope come first, followed by output vocabularies, then the caveats, then pricing/transport. Every sentence carries information, though the terse enumeration style (match modes, risk levels) reads more like a spec dump than guided prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-param nested tool with no annotations and no output schema, the description covers the conceptual model and result enums well. It is still incomplete on the knobs that determine the result (orderSensitive, fieldMapping) and on when 'indeterminate' is returned, which an agent needs to interpret or tune a call.

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 0% across 7 params (3 required, deeply nested), so the description must compensate. It explains the proposal/approvedActions/execution relationship and signals that proposal.description is not the action list (useful semantic guidance), and mentions value/targets/selectors/parameters. But abi, chainId, orderSensitive, and fieldMapping — which materially change the comparison — are never explained.

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?

States a specific verb+resource: compare the structured actions in a caller-supplied DAO proposal against caller-supplied execution calls, and names exactly what is compared (targets, selectors, decoded parameters, native value). Clear enough for an agent to select it, but it never distinguishes itself from the sibling crypto-governance_execution-risk-score, so the agent must infer the boundary itself.

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?

Implies the situation clearly: you have a proposal (with approvedActions) plus the execution calls and want a match verdict. It also sets expectations about what this tool will NOT do (no chain query, no approval/execution inference). No explicit exclusion or named alternative versus risk-score, so it falls short of a 5.

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