Skip to main content
Glama

Get credit purchase

get_credit_purchase
Read-onlyIdempotent

Read a credit purchase's status, amount and whether credit was granted. Requires scope 'billing:checkout'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "purchase_id": "<purchase_id>"
    },
    "name": "get_credit_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
purchase_idYes

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, closed-world behavior, so the description adds real value by stating the required auth scope and enumerating what the response conveys (status, amount, credit granted). It omits edge behavior such as what happens for an unknown or non-existent purchase_id.

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

Conciseness5/5

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

Two short sentences, action first, prerequisite second, no filler. Every clause carries information the agent needs.

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?

With no output schema, the description usefully summarizes the returned data and covers the auth requirement, which is what a simple read-by-id tool needs. The remaining gap is the undocumented parameter and not-found behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter; the schema only supplies type string and format uuid. The description never mentions purchase_id or identifies it as the purchase identifier, leaving the agent to infer it from the tool name.

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 verb ('Read') plus the resource ('a credit purchase') and even names the fields surfaced (status, amount, credit granted), so it is distinguishable from siblings like create_credit_purchase or get_board_pass_purchase. It stops short of explicitly contrasting itself with those siblings.

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 scope prerequisite ('Requires scope billing:checkout') is stated, and single-record lookup keyed by purchase_id implies when to use it, but there is no explicit when/when-not guidance and no pointer to siblings such as get_order or get_plan_purchase for other purchase types.

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