Skip to main content
Glama

Read subscription usage

subscription_usage
Idempotent

Fetch usage from the provider for one of your subscription connections. Never send authorization secrets through MCP.

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": {
      "workspace_id": "<workspace_id>",
      "connection_id": "<connection_id>"
    },
    "name": "subscription_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace id (from whoami).
connection_idYesYour connection id from list_subscriptions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotent, non-destructive, open-world behavior; the description adds that the data comes from the external provider and a security caution about secrets. It does not explain why readOnlyHint is false for a fetch operation, nor anything about rate limits, failure modes, or return content.

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?

Two short sentences, front-loaded with the action and scope; the security caution earns its place but is slightly tangential to invocation.

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 two-parameter, no-output-schema tool the description is adequate, but with no output schema it leaves the shape of the returned usage data entirely unspecified and gives no hint about what the provider call may entail.

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?

Schema coverage is 100% and both parameters are documented in-schema (workspace_id from whoami, connection_id from list_subscriptions). The description adds no meaning beyond 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?

"Fetch usage from the provider for one of your subscription connections" gives a specific verb (fetch) and resource (provider usage) with scope narrowed to a single connection. It does not explicitly contrast with list_subscriptions, which is the nearest sibling, so it falls short of full differentiation.

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

Usage Guidelines3/5

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

"for one of your subscription connections" implies a per-connection call, and the schema points to list_subscriptions for obtaining connection_id, but the description itself gives no when-to-use vs when-not guidance or prerequisites.

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.

Resources