Skip to main content
Glama

Subscription status

subscription_status
Read-onlyIdempotent

[read-only] The current plan and Embers balance of the connected flayr account, with the link where the owner manages billing. (Wraps GET /api/v2/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": "subscription_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the '[read-only]' prefix is largely redundant. The description does earn its place by disclosing the response contents (plan, Embers balance, billing link) and by identifying the underlying endpoint GET /api/v2/billing/subscription, which helps an agent understand it is a pure fetch. It does not cover behavior in edge cases such as a missing or disconnected account.

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 returned data before the endpoint note. Every clause carries information: what is returned, whose account, and where billing is managed. The only slack is the '[read-only]' tag duplicating the annotation.

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 input schema and no output schema, the description has to carry the return-value burden, and it does by listing plan, balance, and billing link. It omits any note on error or unauthenticated states, which is the main remaining gap for an agent calling this cold. Overall it is sufficient for a simple read tool.

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 zero parameters, so there is no parameter meaning for the description to add; the baseline for a parameterless schema applies. Nothing in the description misleads about inputs, and it correctly implies no arguments are needed.

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 concrete resource and payload: the current plan, the Embers balance, and the billing-management link for the connected flayr account. That is far more specific than the title 'Subscription status' and lets an agent recognize it as a billing-read tool. It stops short of differentiating itself from adjacent account tools such as account_trial_get, so it lands 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 Guidelines3/5

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

Usage is only implied: an agent infers it should call this when it needs plan or balance information for the connected account. There is no explicit when-to-use statement, no exclusion, and no named alternative for trial or store-status queries. For a zero-parameter read tool the inference is easy, but the guidance is not written down.

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