Skip to main content
Glama
OrcaRail MCP

OrcaRail MCP

Official
by OrcaRail

subscriptions.retrieve

Read-only

Fetches a subscription by ID so you can inspect its current status, plan, and billing details.

Instructions

Retrieve a subscription by ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "subscriptions.retrieve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubscription ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.1
    • addedInput schema / properties / id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,128}$"
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing further: it does not say what is returned, how a missing/invalid ID is handled, or whether permissions or a specific account mode are required.

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?

A single seven-word sentence with zero filler and the identifying detail front-loaded. It is appropriately sized, though its brevity reflects under-specification rather than tight editing of richer content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with annotations covering safety and a fully documented schema, this is adequate but thin. An agent still cannot tell from the description what the response contains or how an unknown ID behaves.

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?

With one parameter at 100% schema description coverage (including a regex pattern and 'Subscription ID' description), the schema already carries the semantics. The phrase 'by ID' merely restates 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?

Specific verb (Retrieve) plus resource (a subscription) with the key qualifier 'by ID', which distinguishes it from subscriptions.list / subscriptions.update / subscriptions.cancel without needing to name them. It stops short of explicitly contrasting with those siblings, so it sits at 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance and no reference to alternatives such as subscriptions.list. 'By ID' weakly implies a direct single-resource lookup, but the description offers no conditions, prerequisites, or exclusions for an agent to act on.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.