Skip to main content
Glama

get_user_plan

Read-onlyIdempotent

Obtiene el plan de suscripción del usuario (Free, Hobby, Pro) y qué incluye.

Usar cuando el usuario pregunta:
- "¿qué plan tengo?"
- "¿cuáles son mis límites?"
- "¿puedo hacer X?" (donde X depende del plan)

Retorna: plan_id, plan_name, source (de dónde vino el plan: paddle, promo, admin),
started_at y features (el objeto con lo que incluye: booleanos por función y
topes numéricos como storage_mb, workspaces, transcription_hours; una clave
ausente o en null significa SIN TOPE).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered; the description goes further by disclosing the return shape and the non-obvious rule that a missing or null feature key means 'SIN TOPE'. It does not discuss caching, plan freshness, or failure modes, which keeps it below a 5.

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?

Purpose is front-loaded in one sentence, followed by usage triggers and then return fields in a predictable order. The bulleted example questions and the long parenthetical about feature keys add length, but each carries real decision value rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry the return contract itself, and it does: it names plan_id, plan_name, source with its enumerations, started_at, and the features object with its null-means-unlimited convention. For a zero-parameter read tool with annotations already covering safety, nothing an agent needs is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description spends its space on output semantics instead, which is the right allocation.

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?

States a specific verb and resource — 'Obtiene el plan de suscripción del usuario' — and enumerates the possible values (Free, Hobby, Pro) plus the scope ('qué incluye'). An agent knows exactly what this returns without consulting anything else.

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?

Gives three concrete user-question triggers, including the important '¿puedo hacer X?' case where plan gating matters, which is genuinely actionable routing guidance. It stops short of naming exclusions or alternatives (e.g. when to prefer get_user_profile instead), so it is clear context without full when-not coverage.

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