Veynod

Set Budget

set_budget

Set daily limits on a token you issued (or below). null = only the ancestors' limits apply; a limit above the parent's is refused (422).

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": {
      "token_id": "<token_id>"
    },
    "name": "set_budget"
  }
}

Input Schema

Name	Required	Description
`writes`	No
`queries`	No
`token_id`	Yes
`idempotency_key`	No	Optional. Retries with the same key and arguments within 24 h replay the first result (replayed=true) without a second write; a different body with the same key is idempotency_key_reused.
`embedding_tokens`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses the null-clears-own-limit semantics and the 422 refusal when a limit exceeds the parent's — useful failure-mode context. It does not say whether the call replaces or merges existing limits across the three dimensions.

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 dense sentences with the core action front-loaded and the constraint clauses following. The 'null = ...' fragment is compressed to the point of being slightly cryptic, but nothing is wasted.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the hierarchy rules are covered. What remains missing for a mutation tool is merge-vs-replace behavior and per-dimension semantics, which an agent needs before calling it safely.

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?

Schema coverage is only 20%, so the description must compensate. It does add real meaning for token_id ('a token you issued (or below)') and for the null case ('only the ancestors' limits apply'), but it never explains writes/queries/embedding_tokens individually, their units, or whether omitted fields are cleared or left unchanged.

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?

States a specific verb and resource: 'Set daily limits on a token you issued (or below)'. The hierarchy qualifier distinguishes it from a plain budget read and hints at the sibling get_budget/list_budgets, but it never names an alternative explicitly.

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?

Usage is implied by the verb and the parent-cap rule, which tells the agent this is the tool for narrowing a child token's allowance. There is no explicit when-to-use/when-not guidance and no pointer to set_policy or issue_child_token as related operations.

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

All Veynod 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.