Veynod

Renew Token

renew_token

Extend a descendant's expiry (never your own; never past your own expiry).

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>",
      "ttl_seconds": "<ttl_seconds>"
    },
    "name": "renew_token"
  }
}

Input Schema

Name	Required	Description
`token_id`	Yes
`ttl_seconds`	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.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations, which only indicate a non-read-only, non-destructive mutation, the description adds critical authorization and ceiling behavior: the target must be a descendant token and the new expiry cannot exceed the caller's own expiry. It does not discuss error cases or idempotency in the description, but the idempotency key is already documented in the schema.

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?

The description is a single front-loaded sentence with no wasted wording. The core action and its two constraints are immediately visible.

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?

The tool is a mutation with an output schema and safety annotations, so the description need not explain return values or destructive behavior. However, given the low schema description coverage, it should say more about the required parameters and failure conditions to be fully complete.

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 33%, so the description must compensate for undocumented token_id and ttl_seconds. It partially does so by implying token_id must identify a descendant token and that ttl_seconds is bounded by the caller's own expiry, but it does not explain formats, units, or the exact relationship between the parameters.

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 states a specific verb, 'Extend,' and a specific resource, a 'descendant's expiry,' with two important scope limits. It is clear what the tool does, though it does not explicitly name sibling alternatives or say 'token' outright.

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?

The description gives useful exclusions: never renew your own token and never extend past your own expiry. It does not explicitly state when to choose this over related tools such as issue_child_token, revoke_token, or rotate_token_secret, so usage guidance is implied rather than complete.

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.