Skip to main content
Glama

Veyra Trust

veyra_check_endpoint

Read-only

Check the live USDC offer for an x402 endpoint on Arc mainnet before paying. Returns an unsigned verdict and evidence.

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_check_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoIf omitted, use the live offer or catalogue method.
resourceYesHTTPS x402 resource URL.
budgetUsdcNo
capabilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description usefully adds that the verdict is unsigned (no payment is executed) and that evidence is returned alongside it. It says nothing about offer freshness/expiry, latency, caching, or failure behavior when an endpoint has no live offer, which are the remaining unknowns for a pre-payment check.

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 action and the pre-payment timing front-loaded; no filler. It is economical, though the terseness trades off against the undocumented parameters.

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?

For a four-parameter tool with no output schema and half its parameters undescribed, the definition leaves too much open: what budgetUsdc and capability constrain, what 'evidence' contains, and what happens when no live offer exists. An agent could construct a call but not predict the verdict or understand two of its inputs.

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%: method and resource are documented in the schema, but budgetUsdc and capability have no description anywhere. The description adds no meaning for any parameter and does not explain the relationship between budgetUsdc (capped at 5) and the returned offer, or what a capability select is.

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 names a specific verb ('Check') and a precise resource ('the live USDC offer for an x402 endpoint on Arc mainnet'), so an agent knows this retrieves pricing/offer data rather than history or a resource list. It does not name or contrast with sibling tools (veyra_endpoint_history, veyra_list_resources), leaving that differentiation implicit.

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?

'Check ... before paying' gives a clear triggering condition for when to call this tool. It stops short of stating when NOT to use it or naming an alternative for past/aggregate lookups, which would be required for a 5.

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.