perseus

perseus_tokens

Destructive

Control the token budget for rendered context using the @tokens directive, ensuring AI interactions stay within defined limits.

Instructions

Embed token budget for rendered context

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

Input Schema

Name	Required	Description	Default
`args`	No	Arguments for @tokens directive

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.0.10Jun 27, 2026

TDQS

C2.6/5.0

Behavior2/5

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

The description does not explain what 'embed' does or any side effects. Annotations indicate destructiveHint: true, but the description doesn't clarify if tokens are consumed or if state changes. No additional transparency.

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?

The description is very short (5 words), which is concise, but may be under-specified. It is front-loaded but lacks detail that would help an agent.

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?

Given the tool has no output schema and a destructive hint, the description is insufficient. It doesn't explain the effect of the tool, how to use the args parameter, or what happens after invocation.

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 100% with one parameter 'args' described as 'Arguments for @tokens directive'. The description adds no extra meaning beyond the schema's existing documentation.

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

Purpose3/5

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

The description 'Embed token budget for rendered context' provides a verb and resource but is vague. It's unclear what 'embed token budget' entails exactly. Sibling tools have similar naming patterns, so it's not distinguished.

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?

No guidance on when to use this tool versus alternatives like perseus_memory or perseus_tool. No context on prerequisites or typical use cases.

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