Skip to main content
Glama

Account: Get subscription

account_get_subscription

Show the authenticated Nilyo user's login email, plan, trial/subscription status, account limits, team seats and members, plus the available billing actions (subscribe, upgrade, add seats, invite). Use to verify which Nilyo login the agent is connected to, when the user asks about their plan, trial, price, seats, team, why an action is blocked, or before proposing an upgrade. For clients that allow billing links, this may create a Stripe portal session for a paid subscription. ChatGPT receives only current account and entitlement status. Never exposes payment details.

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": "account_get_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description explains why readOnlyHint is false even though the tool appears to be a getter: for paid subscriptions on link-capable clients it may create a Stripe portal session. It also states the privacy boundary (never exposes payment details) and what ChatGPT actually receives. This is exactly the extra context annotations cannot convey.

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-loads the returned data, then the usage triggers, then the side-effect and privacy caveats, which is the right ordering for an agent. Slightly long, and the final two sentences about ChatGPT receiving only entitlement status and payment details never being exposed overlap somewhat.

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?

With no input parameters and no output schema, the description carries the full load and does so by enumerating the fields returned. It also covers the non-obvious side effect and the privacy constraint, leaving nothing material an agent needs before calling it.

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 the schema carries nothing for the description to clarify. Baseline applies; there is no parameter-level meaning to add or omit.

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?

Names a specific verb (Show) and enumerates exactly what is returned: login email, plan, trial/subscription status, limits, seats, members, and billing actions. The read-only framing plus the sibling names (account_change_plan, account_start_subscription, team_add_seats) make it easy to tell this is the inspection tool rather than a mutation tool.

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 trigger conditions: verify which login is connected, user asks about plan/trial/price/seats/team, diagnosing why an action is blocked, and before proposing an upgrade. It stops short of naming the sibling tools to use when the user actually wants to change something, so the exclusions are implied rather than explicit.

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.