Skip to main content
Glama
Sign In

Veynod

by io.github.veynod
OverviewDiscussionsAdmin

Get Token

get_token
Read-only

Inspect a token without its secret: kind, depth, scopes, namespaces, expiry.

token_id="self" (default) is the calling token. A token may inspect itself,
its ancestors and its own subtree; humans and the workspace key see all.

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

Input Schema

NameRequiredDescriptionDefault
token_idNoself

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds useful behavioral context: the secret is omitted and access is constrained by token hierarchy. It could say more about failure modes, but the key safety and visibility behavior is disclosed.

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?

Two compact sentences, front-loaded with the operation and key constraint. Every sentence adds relevant information without repetition.

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?

An output schema exists, so return values need not be fully explained, and the description covers read-only inspection, fields, and access scope. It lacks explicit routing guidance versus alternatives, leaving a minor gap.

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?

With 0% schema description coverage, the description must explain the lone parameter; it clarifies that token_id defaults to "self" and refers to the calling token, with access implications. It does not specify token ID format, so not a 5.

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, "Inspect," and resource, "token," and lists the fields returned while noting the secret is omitted. It does not explicitly distinguish itself from sibling tools such as list_token_tree, so it falls short of a 5.

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?

Explains the token_id="self" default and the visibility scope: self, ancestors, subtree, with humans and workspace key seeing all. It does not explicitly say when to use this tool versus token-tree or other token-related siblings.

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

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