Skip to main content
Glama

get_token_usage

Read-onlyIdempotent

Obtiene estadísticas de uso de tokens de IA del workspace por fecha y función.

Usar para: ver cuántos tokens se consumieron, auditar costos de IA, monitorear el uso del plan.
Retorna totales agregados + filas individuales por función y fecha.

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

Input Schema

NameRequiredDescriptionDefault
daysNoDías hacia atrás (default: 30)
workspace_idNoUUID del workspace, o su nombre tal como lo dice el usuario ('Acme', 'el personal'). Omitir si el token ya tiene workspace fijo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds the return shape ('totales agregados + filas individuales por función y fecha'), which is genuinely useful since there is no output schema, but says nothing about ordering, pagination or volume limits beyond the schema's 90-day cap.

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 short, front-loaded lines: purpose first, then use cases, then return shape. No wasted wording, though the third line could be merged into the first without loss.

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?

For a simple, zero-required-parameter read tool with full schema coverage and annotations, the description covers what it does, when to call it, and what comes back. Missing only edge-case behavior (empty result, workspace not found, truncation), which is minor here.

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 both `days` and `workspace_id` fully documented in the schema, including the name-or-UUID resolution and the default of 30. The description only echoes the 'por fecha' dimension and adds no syntax or format detail beyond the structured fields.

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: 'Obtiene estadísticas de uso de tokens de IA del workspace por fecha y función'. It is clearly distinct from storage/agenda/get_* siblings by domain, though it never names a sibling to differentiate against explicitly.

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?

'Usar para: ver cuántos tokens se consumieron, auditar costos de IA, monitorear el uso del plan' gives concrete use cases that map to real agent intents. It stops short of stating when NOT to use it or pointing to an alternative tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources