Skip to main content
Glama

Pay2GPT

Business: credits and products

business_credits
Read-onlyIdempotent

For a company with a Pay2GPT business API key (sent as Authorization: Bearer ): the remaining activation credits per product, how many openings are in progress against the limit, and the products it can order, by slug.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add context — and it does, by disclosing the required auth scheme and the fact that results are scoped per product including in-progress openings versus a limit. That auth prerequisite is the key operational detail annotations cannot express.

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?

One sentence, no filler, with the authorization precondition front-loaded before the payload. It is dense but every clause carries information; a slightly cleaner split between precondition and return content would read better.

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 carries the burden of describing return content, and it enumerates the three result categories clearly. For a zero-parameter read tool this is essentially complete, though it could note how products and credits relate in the response.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The description correctly signals that scope comes from the API key rather than from any argument.

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 the specific resources returned: remaining activation credits per product, in-progress openings against the limit, and orderable products by slug. That is far more precise than a restatement of the name. It stops short of a clean verb-first statement and never contrasts itself with siblings like list_plans or list_business_orders, so 5 is not warranted.

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?

It gives a clear precondition — a Pay2GPT business API key sent as Authorization: Bearer <key> — which tells the agent who can call it. It does not say when to reach for this tool rather than the order tools (get_business_order, list_business_orders), so the choice between them is left 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