Skip to main content
Glama

BRAINIAC Crypto Governance

Score governance execution drift

crypto-governance_execution-risk-score

Apply caller-supplied transfer and transferFrom calls to the supplied token balances. A transfer that is not in the expected list is unforeseen. The drift index is the share of balances that change. Amounts stay inside the local integer limit. This is not an EVM simulation and no chain is queried. Price $0.04 USDC. POST /api/v1/crypto-governance/execution-risk-score. 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": {
      "sender": "<sender>",
      "calls": "<calls>",
      "balances": "<balances>"
    },
    "name": "crypto-governance_execution-risk-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsYes
senderYes
balancesYes
expectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does add real behavioral context: no chain is queried, amounts are bounded by a local integer limit, the cost is $0.04 USDC, unpaid calls return 402 without executing, and the transport is POST. It stops short of describing error behavior for malformed calls or how unforeseen transfers are surfaced in the result.

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?

Sentences are short and the computational core is front-loaded, with cost and endpoint details placed afterward. The clipped, telegraphic style occasionally reads as under-specified rather than tight, but there is no filler.

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?

There is no output schema and no annotations, so the description must fully specify behavior. It defines the drift index and payment semantics, but omits the shape of the response, handling of the sender field, and error cases for a tool with four parameters and 0% schema coverage.

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%, so the description must compensate. It conveys the meaning of calls (transfer/transferFrom), balances, and expected ('a transfer not in the expected list is unforeseen'), but leaves the required sender parameter entirely unexplained and gives no format or ordering guidance for the arrays.

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 uses a concrete verb ('Apply ... transfer and transferFrom calls to the supplied token balances') and names the core output concept, the drift index. It is clear what the tool computes, though it never explicitly contrasts itself with the sibling governance-execution-diff tool.

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

Usage Guidelines3/5

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

It supplies a scope exclusion ('This is not an EVM simulation and no chain is queried'), which helps an agent decide when not to use it. However, there is no positive guidance on when to prefer this over the sibling diff tool, leaving selection largely 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