Skip to main content
Glama

Get Plans

get_plans
Read-onlyIdempotent

Read the account plans and included access. My Axiocairn read tools: get_dashboard_manifest, get_plans, list_guides, get_guide, get_report_schedule, get_usage_guide, get_alerts, get_alert_conditions. No allowance use, calculation jobs, tool-access records or read-state changes. Account access rules still apply. Other tools may have side effects; check their descriptions.

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

Input Schema

NameRequiredDescriptionDefault
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: explicit exclusions (no allowance usage, no calculation jobs, no tool-access records, no read-state changes) and the caveat that account access rules apply. It does not explain response shape, but with rich annotations a 4 is warranted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, which is good. But half the text is a roster of eight sibling read tools and generic warnings about other tools' side effects, which does not help an agent invoke get_plans and reads as shared boilerplate.

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 one-optional-parameter, non-destructive read tool with full annotations and no output schema, the description covers scope, exclusions, and access caveats. The only meaningful gap is that it does not describe what a plan record contains or how included access is represented in the response.

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?

There is a single optional `language` parameter with an en/zh-Hant enum, and schema description coverage is 0%, so the description could have explained what the language affects. The enum values are self-explanatory in the schema, keeping this at a baseline adequate level rather than a failure. A 3 with annotations covering behavior and a single obvious parameter, but no added meaning, is fair.

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?

"Read the account plans and included access" gives a specific verb (read) and resource (plans, plus included access), so the agent knows this is a billing/entitlement lookup rather than a guide or dashboard read. It stops short of differentiating itself from the named siblings like get_usage_guide or get_dashboard_manifest, so it does not reach 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?

The description places itself in a set of read tools and rules out allowance use, calculation jobs, tool-access records, and read-state changes, which narrows expectations somewhat. However, it never states when an agent should choose get_plans over get_usage_guide, get_dashboard_manifest, or the many analysis tools, and "check their descriptions" pushes routing decisions back onto the caller.

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