Skip to main content
Glama

Current subscription

get_subscription
Read-onlyIdempotent

The account's subscription: plan, status (active, past_due, cancelling, ended), who manages it (admin or lavatop), price and currency, period end, whether it renews, credits and briefs a period. null: no subscription (list_plans, then subscribe). [REST: GET /api/billing/subscription]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's job is return-shape disclosure — and it delivers by enumerating the fields and the null-vs-subscription distinction. It also pins the underlying REST call (GET /api/billing/subscription), which helps an agent correlate responses, but adds nothing about auth requirements or error cases beyond null.

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?

Front-loaded with the resource, then a dense field list, then the null path, then the REST endpoint — all sentences carry information. The phrase 'credits and briefs a period' is compressed to the point of being hard to parse, which is the one place clarity is traded for brevity.

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?

With no output schema, the description must carry the return contract itself, and it largely does by naming every field and the null outcome. Minor gaps remain: the shape of 'credits' and the meaning of 'briefs a period' are not explained, and no pagination/caching behavior is noted for an idempotent read.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly avoids inventing inputs (no account id, no filters), implicitly confirming the call is scoped to the authenticated account.

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 resource (the account's subscription) and enumerates exactly what it returns — plan, status, manager, price, period end, renewal, credits. The status vocabulary (active, past_due, cancelling, ended) and the null case make it unambiguous against sibling readers like get_payment_status or get_account.

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?

Gives concrete guidance for the empty case: if the result is null, call list_plans and then subscribe, which names the actual next-step siblings. It stops short of stating when to prefer a sibling over this call (e.g., payment status lookups), so it is clear context without full exclusions.

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