Skip to main content
Glama

get_quota_and_pricing

Check free trial credits (2 free + 3 w/ email = 5), 5 modules & 7 USD Stripe 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_quota_and_pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_tokenNoOptional GLBH-* Bearer token
guest_tokenNoOptional anonymous session guest token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the content of the response (credit tiers, module count, plan pricing) but says nothing about whether the call is read-only, whether authentication is required, how the optional api_token vs guest_token change the result, or whether any state is mutated.

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?

A single dense sentence with no filler and the key content front-loaded. The parenthetical arithmetic '(2 free + 3 w/ email = 5)' is efficient, though the trailing '5 modules & 7 USD Stripe plans' reads as shorthand that could be clearer.

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

Completeness3/5

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

With no output schema and no annotations, the description must stand alone, and it does convey the broad shape of the returned data. However, it omits auth expectations, the effect of the two optional tokens, and any link to the credit-claiming sibling, leaving gaps for a zero-required-parameter tool.

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 description coverage is 100% and both parameters are optional with their own descriptions ('Optional GLBH-* Bearer token', 'Optional anonymous session guest token'), so the baseline is 3. The description adds no meaning about when a token is needed or how token presence affects the returned quota.

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?

The description names a specific verb ('Check') and enumerates the resources returned: free trial credits, 5 modules, and 7 USD Stripe plans. An agent can tell this is a read-only informational lookup rather than a simulation run, though the phrasing is compressed and the '5 modules & 7 USD Stripe plans' fragment is ambiguous without prior context.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no reference to alternatives. Notably, the sibling claim_email_bonus_credits is the tool that would grant the '+3 w/ email' credits mentioned here, yet the description never routes the agent there or explains the relationship between checking and claiming.

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