Skip to main content
Glama

Base Agent Due-Diligence Kit

Governance Attack Cost calculator (free)

governance_attack_cost
Read-onlyIdempotent

FREE. Free Governance Attack Cost calculator: cost to buy enough votes to pass a malicious proposal. Give slug (modelled dossier) or quorum, plus token price.

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": {
      "price": "<price>"
    },
    "name": "governance_attack_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
varNoValue at risk in USD (optional)
slugNoDossier id with GAC inputs, e.g. moonwell-base
priceYesGovernance token price in USD
quorumNoQuorum in votes (if no slug)
opposingNoVotes expected to oppose (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds only the 'FREE' pricing cue and the fact that a slug refers to a modelled dossier; it does not mention what is returned or how quorum/price interact.

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

Conciseness3/5

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

Short and front-loaded, but 'FREE. Free ... calculator' duplicates the same claim twice, wasting roughly a third of the body on a marketing restatement rather than substance.

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 stateless 5-parameter calculator with full schema coverage and no output schema, the essentials are present. Still missing is any sense of what the result looks like (a single cost figure? a breakdown?) and how the optional var/opposing inputs change it.

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 coverage is 100%, so the baseline is 3, and the description adds genuine meaning beyond it by explaining the slug-or-quorum exclusivity ('slug (modelled dossier) or quorum') and that price is always required alongside. It does not clarify how var or opposing affect the calculation, keeping it short of a 5.

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 and resource: computes the cost to buy enough votes to pass a malicious proposal. That is concrete and distinguishable from the dossier/xray/scan siblings, though it never names an alternative directly.

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?

Gives input-shape guidance ('give slug... or quorum, plus token price'), which implies two valid calling modes, but says nothing about when to choose this versus a sibling or when the result is not meaningful. Usage is implied rather than framed.

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