Skip to main content
Glama

Get Plan Renewal

get_plan_subscription_status
Read-only

Returns each doola plan subscription of the company as the plan and billing page shows it: its price per billing period, status, whether it renews automatically, and renewsOn (next renewal), endsOn (set to cancel, with access until then) or endedOn. Use it for when the plan renews, the next charge and whether a service such as the registered agent is still covered. To cancel, turn off auto-renew or get a refund, point the user to doola support. Answer in plain language and never show the user the field names. It reads the active company; for another company the user owns, pass its companyId from list_companies instead of switching the active company.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
companyIdNoOPTIONAL. The doolaCompanyId (an id like '30E5c1AQA326uOuDlsic4No7zZ5'). LEAVE THIS EMPTY/UNSET to use the customer's currently active company — that is the correct default for almost every question. Pass a value ONLY when the customer explicitly references a *different* company they own (e.g. 'show me transactions for my other company X'). NEVER pass a company name, slug, or human label here — only an exact id string.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description is not carrying the safety burden. It still adds real behavior: it reads the active company by default, and for another owned company the agent should pass that company's id from list_companies instead of switching the active company. It also encodes output semantics (endsOn means set to cancel but access continues until that date) and a presentation rule not to surface raw field names, though it says nothing about empty results or errors.

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?

The definition is front-loaded with what is returned, then use cases, then the support-redirect exclusion, then company scoping. Every sentence has a job, including the plain-language output instruction. It is somewhat long for a single read tool, but no sentence is filler.

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?

This is a read-only tool with four all-optional, fully documented parameters and no output schema, so the description must convey what comes back — which it does by listing the returned fields and explaining the three date-ish states. It also covers cross-company scoping and the hand-off for mutations. Nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%, and the schema already spells out the active-company default and the exact-id requirement for companyId, plus the analytics-only nature of context, llm_model, and conversation_id. The description's line about companyId largely restates that and adds only the pointer to list_companies. With the schema doing the heavy lifting, baseline 3 is appropriate.

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 verb and resource ("Returns each doola plan subscription of the company") and enumerates the returned fields: price per billing period, status, auto-renew flag, and the renewsOn/endsOn/endedOn triplet. That is enough for an agent to tell it apart from status tools for EIN, ITIN, dissolution, or tax filings. It does not explicitly distinguish itself from the sibling get_doola_plan, so it falls short of a 5.

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?

Usage is stated concretely: "Use it for when the plan renews, the next charge and whether a service such as the registered agent is still covered." It also gives an explicit when-not, routing cancellation, auto-renew changes, and refunds to doola support rather than to another tool. No in-product alternative for reading plan data is named, which keeps it just under a 5.

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.