Skip to main content
Glama

Veyra Trust

veyra_endpoint_history

Read-only

Preview the recency and coverage of stored Arc USDC observations. Full history and change details are sold separately.

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": {
      "resource": "<resource>"
    },
    "name": "veyra_endpoint_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoPOST
resourceYesHTTPS x402 resource URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior — results are a truncated preview and complete data is a paid/separate offering — but says nothing about how truncation manifests or about the x402 payment mechanics implied by the resource parameter.

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?

Two short sentences with the core capability front-loaded and no filler. The second sentence could be tightened, but nothing is redundant.

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

Completeness2/5

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

With no output schema, the description must carry the burden of explaining returns, yet 'recency and coverage' is too vague to tell an agent what it will receive. The undocumented 'method' parameter and unaddressed paid-x402 behavior leave meaningful gaps for a two-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description adds no parameter meaning at all. The 'method' enum (GET/POST, default POST) is completely undescribed in both schema and description, and the description does not clarify what an 'HTTPS x402 resource URL' must point to.

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 gives a verb ('Preview') and a resource ('stored Arc USDC observations'), but 'recency and coverage' is an abstract way to describe the output and never states what the tool actually returns. It does not differentiate itself from veyra_check_endpoint or veyra_list_resources beyond a vague 'full history ... sold separately' hint.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no named alternative, despite two plausible siblings in the catalog. The clause about full history being 'sold separately' implies this is a limited preview, but the agent is left to infer when that limitation should route it elsewhere.

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.