Skip to main content
Glama

Pagetool

Payment and domain status

payment_status
Read-onlyIdempotent

Read-only, truthful status of the payments and domains of the customer - use it to tell them exactly where their money and their domain stand.

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

Input Schema

NameRequiredDescriptionDefault
domainNoOptionally narrow to a single domain, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds the claim of 'truthful' status (i.e., authoritative live data) which is modest added value, but says nothing about freshness, failure modes, or what the response contains.

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 compact sentence that front-loads the read-only nature and the resources covered. Slightly promotional wording ('truthful', 'exactly') adds no informational value, but there is no padding.

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 single optional-parameter read tool with full annotation coverage, this is nearly sufficient. The main residual gap is that no output schema exists and the description doesn't hint at what status fields come back, but the scope of the call itself is unambiguous.

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 'domain' parameter is already documented in the schema with an example. The description adds no narrowing semantics or defaults beyond that, 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 verb-and-resource pair: read-only status of the customer's payments and domains. It clearly separates itself from mutation siblings such as domain_register or purchase_execute, though it doesn't explicitly name an alternative status tool (publish_status) to contrast with.

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 phrase 'use it to tell them exactly where their money and their domain stand' implies the use case (answering customer billing/domain questions), but there is no explicit when-not guidance and no named alternative for related lookups.

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