Skip to main content
Glama
Sign In

Pacta

by io.github.Fractal-Neurons
OverviewDiscussionsAdmin

Governance proposal pinned-vs-live diff

pacta_scan_proposal_diff
Read-onlyIdempotent

Re-runs the pinned contract reads of a Pacta-tracked governance proposal (Aave, Euler, Morpho, Sky) at the live block and returns pinned-vs-live diffs. Free during the launch (no key, no payment).

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": {
      "forum": "<forum>",
      "topicId": "<topicId>"
    },
    "name": "pacta_scan_proposal_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
forumYesGovernance forum
topicIdYesForum topic id; the proposal must be listed in https://pacta.wtf/api/v1/proposals.json as <forum>-<topicId>

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 genuinely new behavioral context beyond them: it re-reads at the live block (hence results are time-sensitive), and it is free during launch with no key or payment required. It does not say what happens when a proposal is not tracked or how large a diff response can be.

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

Conciseness5/5

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

Two sentences, both earning their place: the core action and scope come first, the cost/auth note second. No filler or restatement of the title.

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, so the description carries the burden of explaining return values, and 'returns pinned-vs-live diffs' is thin — it does not say what a diff entry contains or how a not-tracked proposal is reported. Annotations cover safety and the cost note covers access, but the response shape remains underspecified for a diff tool.

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 both parameters are already documented, including the enum and the topicId pattern. The description only echoes the forum list already present as an enum and does not add format or constraint detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource: re-runs pinned contract reads of a Pacta-tracked governance proposal at the live block and returns pinned-vs-live diffs. It names the four supported forums (Aave, Euler, Morpho, Sky), which lets an agent distinguish this from the timelock, control-plane and preflight siblings without opening the schema.

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?

The purpose implies when the tool is useful (checking whether a proposal's pinned reads have drifted from live chain state), but there is no explicit when-to-use or when-not-to-use statement and no named alternative among the siblings. An agent must infer the selection rule from the verb 're-runs ... diffs' alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pacta toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources