Skip to main content
Glama

list_client_subscriptions

Read-only

A client's plan subscriptions with you (current and past): plan, status, renewal status, period end and any pauses.

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": {
      "clientId": "<clientId>"
    },
    "name": "list_client_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdYesClient's User _id (from list_clients)
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and data locality are covered without the description's help. The description adds real value by disclosing the returned attributes (plan, status, renewal status, period end, pauses), which matters since there is no output schema. It says nothing about ordering, result volume, or how pagination affects completeness.

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 tight sentence, front-loaded with the scoping subject and resource, then the field list. Every clause carries information. It is a sentence fragment rather than a full clause with a verb, which is a small polish issue but does not hurt comprehension.

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 two-parameter read tool with no output schema, the field enumeration is exactly the compensating detail an agent needs to judge relevance. The remaining gap is pagination behavior, which the description ignores entirely. Safety semantics are already handled by annotations, so nothing else critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: clientId is documented in the schema, but the nested pagination object (pageSize, pageNumber) carries no descriptions anywhere. The description does not mention pagination at all, so an agent gets no cue that results are paged or how to walk them. It adds nothing beyond what the schema already states about clientId.

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 names a specific resource scoped to one client ('A client's plan subscriptions with you') and enumerates what each entry contains: plan, status, renewal status, period end, pauses. That is enough to distinguish it from a generic subscriptions listing and from the other list_client_* siblings. It never explicitly contrasts with list_subscriptions, but the client scoping plus the current-and-past framing is clear.

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 guidance: nothing says whether to reach for this versus list_subscriptions, nor any prerequisite beyond the schema-level note that clientId comes from list_clients. The '(current and past)' parenthetical hints at scope but is a data fact, not a usage rule. The agent must infer selection from the name alone.

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.