Skip to main content
Glama
Sign In

VEYA

by io.github.veyanet
OverviewDiscussionsAdmin

veya_tier

Your $VEYA account tier and the limits it sets on the product API: daily actions, daily receipts, receipt history window and API key rate per minute, plus today's use. The tier comes from the $VEYA held by your sign-in wallet plus up to 3 linked wallets on Robinhood Chain mainnet. Without a key, returns the public tier table.

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": "veya_tier"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNoProduct API key (veya_dev_… / veya_live_…). Mint on the product site. Guest JWT is not a write credential.
sessionTokenNoOptional guest JWT for Use listing only. Prefer apiKey.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that the tier derives from $VEYA held by the sign-in wallet plus up to 3 linked wallets on Robinhood Chain mainnet, and that omitting a key returns the public tier table. It does not discuss caching, freshness, or auth failure behavior, but it is substantially more transparent than a bare label.

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

Conciseness5/5

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

Three compact sentences, front-loaded with what the tool returns and followed by derivation and fallback conditions. Every sentence adds concrete information and there is no repetition or filler.

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?

For a read-only tool with two optional parameters and no output schema, the description gives enough to understand the returned data: tier limits, today's use, and the public fallback table. A little more on output shape or freshness would help, but the core contract is covered.

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?

Schema coverage is 100%, so the schema already documents both optional parameters in detail. The description adds meaningful behavior for the apiKey parameter: omitting it yields the public tier table instead of personalized limits. It does not mention sessionToken, but the key omission behavior is useful extra semantics beyond the schema.

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

Purpose5/5

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

The description states a specific resource and scope: the caller's $VEYA account tier and the API limits it determines (daily actions, receipts, history window, rate per minute) plus today's usage. It is clearly a read operation returning tier and quota data, which an agent can distinguish from generic account or health tools even without naming a sibling.

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?

It implies usage by explaining the no-key fallback ('Without a key, returns the public tier table'), which helps an agent know what happens when omitting apiKey. However, it does not explicitly say when to use this versus related tools like veya_account or veya_writes_status, nor does it give exclusions or prerequisites for calling it.

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