Skip to main content
Glama

Get account allowance

get_account
Read-onlyIdempotent

Use this when the user asks about their VoxTale plan, allowance or limits, including asks to upgrade, change or buy a plan, or about pricing ("how many do I have left", "upgrade me to yearly"). Returns features, used and remaining generations and edits, the reset date, and planChanges: plans cannot be changed in chat. Answer from this result as plain facts; give no links or directions for changing a plan. Does not create an account or change or sell plans.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planChangesYes
entitlementsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / planChanges
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "entitlements"
      -]New value: +[
      +  "planChanges",
      +  "entitlements"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with that safe-read profile. Beyond annotations it adds genuinely non-obvious behavior: the response includes a planChanges field signalling plans cannot be altered in chat, and the agent must answer plainly without links or upgrade directions. The only reason this is not a 5 is that the return-value listing overlaps with the existing output schema.

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?

It is front-loaded with the trigger condition first, then the returned fields, then the constraint about plan changes. The single dense paragraph packs several distinct obligations (answer plainly, no links, no plan sales) which slightly hurts scanning, but no sentence is redundant.

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 parameters, rich annotations, and an output schema handling return structure, the remaining burden is when-to-use and what-not-to-promise — and the description covers both explicitly. An agent has everything needed to call this correctly and answer from its output.

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?

There are zero parameters, so per the baseline this scores 4 with no param semantics needed. The description correctly adds no invented arguments and notes the empty-input nature implicitly by describing a pure read of account state.

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 names the exact resource ('VoxTale plan, allowance or limits') and enumerates what is returned: features, used and remaining generations and edits, reset date, and planChanges. It further distinguishes itself negatively by stating it 'Does not create an account or change or sell plans,' which separates it from sibling mutation tools like create_generation or edit_thumbnail.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('when the user asks about their VoxTale plan, allowance or limits') and backs it with concrete example utterances ('how many do I have left', 'upgrade me to yearly'). It also states the boundary cases — upgrade/pricing questions route here, but no plan change is possible — leaving nothing to inference.

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