Skip to main content
Glama

Pro key status

get_pro_status
Read-only

Check whether a RugRadar Pro API key is valid and when it expires, plus the current free and Pro limits.

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_pro_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoRugRadar Pro API key (optional; alternatively send Authorization: Bearer <key>).

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 readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real value beyond that by disclosing the returned information (key validity, expiry timestamp, current free and Pro limits) for a tool with no output schema, which is exactly the missing piece an agent needs.

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?

A single well-formed sentence with no filler, front-loading the primary purpose (key validity and expiry) before the secondary limits information. Nothing is wasted.

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 low-complexity read-only check with no output schema, the description covers both the validation result and the limits payload. It could go slightly further by noting the call works without a key (falling back to the Authorization header) or what happens when the key is invalid, but nothing essential is missing.

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?

There is one optional parameter with 100% schema coverage, and the schema already explains the Authorization: Bearer alternative. The description adds nothing about the api_key parameter, so 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: 'Check whether a RugRadar Pro API key is valid and when it expires,' plus a secondary payload of 'current free and Pro limits.' This clearly distinguishes it from siblings like get_pro_quote or verify_payment_and_get_key, though it never names or explicitly contrasts with them.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance appears. The agent is not told, for example, to call this before other Pro endpoints to confirm the key is valid, or that verify_payment_and_get_key is the tool for obtaining a key in the first place.

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.