vordium-mcp

Agent policy

get_policy

Read-onlyIdempotent

Each agent's policy and market limits as the chain stores them, and whether the network enforces them now. Ask: "What limits does my agent trade under?"

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": {
      "address": "<address>"
    },
    "name": "get_policy"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	No	optional agent address
`address`	Yes	the owner account

Output Schema

Name	Required	Description
`count`	No
`owner`	No
`agents`	No
`network`	Yes	testnet or mainnet
`summary`	Yes	one plain sentence
`available`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent operation. The description adds value by defining the scope of the data (policy and limits) and the state it reflects (enforcement status), which is useful context beyond the hints.

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?

The definition is highly concise. It uses two sentences, front-loading the definition of the data and concluding with a clear, actionable prompt for the user.

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?

Given that the tool is a simple retrieval function and its safety characteristics are covered by annotations, the description provides all necessary context for an agent to correctly select and invoke the tool for policy lookup.

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?

With 100% schema description coverage, the parameters are well-defined in the input schema. The description does not add functional meaning or constraints to the parameters themselves, thus meeting the baseline score.

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 clearly states the resource being retrieved—the agent's policy and market limits—and adds the crucial detail that it reports on network enforcement status. It avoids being a mere tautology of the tool name.

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 description provides a conceptual use case by posing the question, 'What limits does my agent trade under?' However, it does not explicitly state when to use this tool versus other related getter tools in the ecosystem.

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

All vordium-mcp 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.