Skip to main content
Glama

Current service and payment capabilities

get_service_status
Read-only

Read live free-credit policy, trial confirmation requirements, card/crypto checkout availability, package prices and documentation links. Public, no key, no credits. Does not create an order or pay anything. Check this before offering crypto.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is known, yet the description still adds material context they do not carry: 'Public, no key, no credits' (no authentication or credit cost) and 'live' (freshness of the returned policy). It does not describe rate limits or the shape of the response, but for a zero-parameter read that is a modest gap.

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, front-loaded with the verb and the returned content, followed by the negative capability and the one usage trigger. No filler and nothing buried.

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 parameters, no output schema but an open-world read, the description supplies what an agent needs to decide to call it: what it returns, that it is free and keyless, and that it has no side effects. Only the practical trigger for calling it beyond crypto (e.g. checking trial or price before register_account/buy_credits) is left unstated.

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 zero parameters, so the baseline is 4. The description correctly implies no input is required by noting it is public and needs no key, matching the empty schema rather than contradicting it.

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 opens with a specific verb ('Read') and enumerates the resource contents concretely: free-credit policy, trial confirmation requirements, card/crypto checkout availability, package prices, documentation links. This is far more informative than the title alone. It stops short of distinguishing itself from the sibling get_packages, which plausibly overlaps on package prices.

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?

'Check this before offering crypto' gives an explicit trigger condition an agent can act on, and 'Does not create an order or pay anything' implicitly routes ordering/payment to a different tool. What is missing is a direct naming of that alternative (e.g. buy_credits) or an upfront statement of when not to bother calling it.

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.