Skip to main content
Glama
Sign In
Unreal-MCP

Unreal-MCP

by aadeshrao123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_mcp_token_stats

Retrieve accumulated per-command token usage statistics sorted by highest estimated tokens. Enable debug mode first with set_mcp_debug.

Instructions

Get accumulated per-command token usage statistics.

Returns commands sorted by max_estimated_tokens (worst offenders first). Each entry shows: call_count, avg/max/total estimated tokens, response chars.

Enable debug mode first with set_mcp_debug(enabled=True).

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_mcp_token_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4.4/5.0
Behavior4/5

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

Describes the return format (commands sorted, fields like call_count, avg/max/total estimated tokens, response chars). With no annotations, it provides good behavioral context, though could mention if stats reset.

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 concise sentences with no fluff. The most important info (what it does) is first, then details, then prerequisite. Efficiently structured.

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?

Given no parameters and an output schema (implied), the description explains the output structure sufficiently. Could add a note on scope (e.g., session lifetime) but overall complete for a stats tool.

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?

No parameters exist (0 params), so schema coverage is 100%. Description adds no param info as none needed. Baseline score of 4 for zero parameters.

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 clearly states it retrieves 'accumulated per-command token usage statistics' and specifies the sorting order, distinguishing it from all other sibling tools that deal with assets, blueprints, Niagara, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly mentions a prerequisite: 'Enable debug mode first with set_mcp_debug(enabled=True).' This tells the agent when to use it (after enabling debug). No need for alternatives as it is unique.

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

Deploy Server

Other Tools