Skip to main content
Glama

Lovie Company Formation

List Billing Subscriptions

lovie_billing_list_subscriptions
Read-only

Lists the company's recurring Lovie charges (the Equity/CapTable plan, domain auto-renewals) with price, status, renewal or end date and the card each one charges.

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": {
      "companyId": "<companyId>"
    },
    "name": "lovie_billing_list_subscriptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
subscriptionsNo
stripeUnavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds domain context (recurring charges, which card is charged, renewal vs end date) beyond the annotations, but says nothing about scoping, pagination, or whether all companies' subscriptions are returned.

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?

A single front-loaded sentence with no filler; every clause (plan types, price, status, renewal/end date, charged card) contributes information about the result set.

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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile. However, for a list tool sitting beside get_overview, get_subscription, list_invoices and list_purchases, the description leaves the selection boundary and result scoping unaddressed.

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% for the single companyId parameter, so the schema carries the parameter burden and this is the baseline case. The description does not explain whether companyId must be the caller's own company or can be any company, which is the one piece of meaning it could have added.

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 gives a specific verb and resource ('Lists the company's recurring Lovie charges') and enumerates the concrete subscription types covered (Equity/CapTable plan, domain auto-renewals) plus the fields returned. That is enough for an agent to tell it apart from invoice or purchase listings, though it never names the sibling tools it competes with.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite statement, and no routing to alternatives such as lovie_billing_get_subscription for a single subscription or the invoice/purchase list tools. The agent must infer the boundary from the one-sentence summary alone.

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.