Skip to main content
Glama

Get pay-as-you-go

getPayAsYouGo
Read-only

Pay as you go on this workspace: whether usage past the allowances is billed, the monthly limit and what extras cost so far, the current billing period, the limits that can be chosen and the prices. Only the owner of the workspace reaches billing, through a client connected with every address.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

While annotations handle safety (readOnlyHint: true), the description enhances transparency by defining *what* the agent can expect regarding the output—a comprehensive view of billing and limits. It specifies the operational constraints (owner access) which is a behavioral trait.

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?

The description is dense and highly packed with information, achieving a high level of utility. Although it is slightly wordy, it successfully front-loads the necessary scope and provides crucial constraints in a single, coherent paragraph.

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?

For a read-only, parameter-less data retrieval tool, the description is functionally complete. It thoroughly outlines all categories of information (usage, costs, limits, period) that the agent can expect the tool to return.

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?

Since the input schema contains zero parameters and has 100% coverage, the description has no additional semantic role to play beyond the baseline. A score of 3 is appropriate for a parameter-less tool.

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 provides an exceptionally detailed purpose by listing specific data points retrieved, including billing status ('whether usage past the allowances is billed'), monetary details ('what extras cost so far'), and configuration ('the limits that can be chosen and the prices'). This leaves no ambiguity about the tool's function.

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

Usage Guidelines4/5

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

The description provides a strong usage constraint by stating that only the owner of the workspace can reach billing. This explicitly defines the required user context and permission level necessary for the tool to be meaningful.

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.