Skip to main content
Glama
Sign In

VEYA

by io.github.veyanet
OverviewDiscussionsAdmin

veya_anchor_pq_attestation

Link PQ identity hash to execution hash on Veya.sol from YOUR wallet

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": {
      "environmentUuidHex": "<environmentUuidHex>",
      "identityHashHex": "<identityHashHex>",
      "executionHashHex": "<executionHashHex>"
    },
    "name": "veya_anchor_pq_attestation"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoProduct API key (veya_dev_… / veya_live_…). Required for on-chain writes.
identityHashHexYes
payerPrivateKeyNoUser wallet private key that pays gas. Prefer VEYA_PAYER_PRIVATE_KEY on a self-hosted MCP.
executionHashHexYes
environmentUuidHexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'From YOUR wallet' implies the operation is signed and gas-paid by the caller's own key, but nothing states that this is an irreversible on-chain write, what permissions/API key are required, or what happens on failure. The key behavioral facts are left to inference.

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

Conciseness3/5

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

It is a single, front-loaded sentence with no filler, which is good. But the terseness tips into cryptic phrasing ('YOUR wallet') rather than earning its place with useful detail.

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?

This is a 5-parameter on-chain write with no annotations, no output schema, and 40% parameter coverage. For that complexity the description is far too thin: it omits prerequisites, side effects, and the meaning of three required hash/environment arguments.

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 40%: apiKey and payerPrivateKey are documented in the schema, but identityHashHex, executionHashHex, and environmentUuidHex have no descriptions anywhere. The description mentions no parameter names or formats, so it fails to compensate for the coverage gap on three required fields.

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 gives a concrete verb and resource: it links a PQ identity hash to an execution hash on the Veya.sol contract. That is specific enough to know what the tool does. However, it offers no differentiation from close siblings such as veya_anchor_proof or veya_attest_execution, which an agent could easily confuse it with.

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 guidance on when to use this versus veya_anchor_proof, veya_attest_execution, or veya_register_pq_onchain, and no stated prerequisites. The phrase 'from YOUR wallet' hints at a wallet-signed path but does not define the condition that selects this tool.

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

All VEYA 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