Skip to main content
Glama

Credits left on a key (free)

credits_status
Read-onlyIdempotent

FREE. Credits left, essay markings left and expiry of your key (from the Authorization: Bearer header or the key argument).

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": "credits_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOptional Iris Credits key (iris_ + 48 hex). Better: set it once as the MCP header Authorization: Bearer <key>. Without a key the call is paid with x402 / MPP over MCP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the call is free, and the credential is resolved from the Authorization: Bearer header with the key argument as fallback, which matters for correct invocation. It still does not say what happens on an invalid or expired key.

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 the most decision-relevant token ('FREE') front-loaded and no filler. The telegraphic fragment style ('Credits left, essay markings left and expiry') is compact but slightly clipped, which keeps it just short of ideal.

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 read-only tool with no output schema, the description does the necessary work by enumerating the three returned values and explaining credential sourcing and cost. An agent has enough to call it correctly; only error/expiry edge cases are unaddressed, and the sibling-free framing is a minor gap.

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 the single optional 'key' parameter is fully documented in the schema, including the iris_ + 48 hex format and the header alternative. The description repeats the header-or-argument sourcing but adds no further meaning, so the baseline 3 applies.

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 resource and scope: remaining credits, remaining essay markings, and key expiry, plus the source of the key (Bearer header or key argument). This clearly separates it from siblings like credits_claim, credits_quote and buy_credit_pack, which plausibly perform actions rather than report status, though the description never names them explicitly.

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 leading 'FREE' signals that this call costs nothing, which implicitly tells an agent to check status here before invoking paid paths such as x402/MPP. Beyond that implied cue there is no explicit when-to-use or when-not guidance and no referenced alternative among credits_claim, credits_quote or payment_options.

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