Skip to main content
Glama

get_subscription

Read-only

Get one subscription by ID (from list_subscriptions or an entry's subscription IDs), including its type, unread count and tags. Fails with a not-found error if the user has no active subscription with that 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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "get_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
subscriptionIdYesSubscription ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the failure mode (not-found when the user has no active subscription with that ID) and the shape of the payload (type, unread count, tags). That is meaningful added context; only deeper details like ID format expectations or behavior with inactive subscriptions are left implicit.

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 sentences, front-loaded with the core action and payload, followed by the error condition. No redundant restatement of the name or annotations.

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?

A single-parameter read tool with no output schema; the description compensates by naming the returned fields and the error case. Nothing needed to invoke it correctly is missing.

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?

Schema coverage is 100% and the UUID format is already enforced there, so the baseline is 3. The description earns above baseline by documenting the provenance of subscriptionId, which the schema's bare "Subscription ID" label does not convey.

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?

States a specific verb and resource ("Get one subscription by ID") and explicitly contrasts with the list operation by naming list_subscriptions as the source of IDs. It also enumerates the returned fields, so an agent can distinguish it from its siblings without opening anything else.

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?

Explains where valid IDs come from (list_subscriptions output or an entry's subscription IDs), which is the key selection context. It stops short of an explicit when-not-to-use statement, but the read-one-vs-list-many split is implicit and clear.

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.