AgentWorld

tgov_info

[FREE] TGOV - Treasury Governance Coordination for multi-agent capital deployment. Takes a fleet of agents each requesting to deploy treasury capital (risk tier 1-5, mandate cap, requested amount), the current market state (volatility percentage), and an optional set of governance rules; returns the coordinated deployment decision for every agent plus a full audit log. Rules fire on threshold crossings (volatility above 15 caps high-risk tiers at 50 percent, above 30 pauses them, above 60 freezes all - default pack). Verdicts: CLEAR, ADJUSTED, PAUSED, FREEZE (worst case wins). This tool returns service info and terms. The paid decision endpoint is https://agentpaystore.com/tgov/api/coordinate (POST, $0.05 USDC via x402 on Base L2, HTTP 402 without X-Payment).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tgov_info"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It states the tool is "[FREE]" and returns service info and terms, and it describes the paid endpoint's payment flow, but it does not describe rate limits, auth requirements, or other operational traits of this info tool.

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

Conciseness2/5

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

The description is overlong and back-loads its actual purpose, leading with a lengthy explanation of the paid coordination endpoint. For a simple info tool with an empty schema, most of the text about risk tiers, volatility thresholds, and verdicts does not earn its place.

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

Completeness4/5

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

Since an output schema exists, the description need not explain return values. It sufficiently clarifies that this tool returns service info and terms, providing context about the TGOV service and the paid endpoint. The only gap is the muddled focus, but the core purpose is stated.

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?

The tool takes zero parameters, so parameter semantics are not applicable and the baseline score of 4 is appropriate. The description's detailed parameter list belongs to the paid endpoint, not this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's actual purpose only at the end: "This tool returns service info and terms." Most of the text instead details a separate paid decision endpoint, which could lead an agent to mistake this tool for the coordination service 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?

It explicitly identifies the alternative for actual decisions: the paid endpoint at agentpaystore.com/tgov/api/coordinate. The condition (service info vs. paid decision) is clear, though it does not state explicit when-not-to-use guidance for this info tool.

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

All AgentWorld tools Inspect

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

Need Help?