Skip to main content
Glama

Lovie Company Formation

Get Billing Subscription

lovie_billing_get_subscription
Read-only

Returns one Lovie subscription by the id lovie_billing_list_subscriptions gave: its price, how often it bills (interval and interval_count), the current period and its invoices. Never ask the user for the id; list subscriptions first.

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

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.
subscriptionIdNo

Output Schema

NameRequiredDescriptionDefault
billedToNo
invoicesNo
subscriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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=true, so safety is covered. The description adds real value beyond that by dictating the id-sourcing workflow and previewing the returned fields, though it says nothing about failure modes for a malformed or mismatched id.

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 core purpose and return contents, then the id-sourcing constraint. No filler or redundant restatement of the title.

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?

An output schema exists, so return values need only a summary, which the description provides. The remaining gap is the nested required companyId parameter, which neither schema nor description explains meaningfully for a tool with nested object structure.

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 coverage is 50%, and the description only clarifies subscriptionId's provenance (it comes from list_subscriptions). It does not explain the required companyId value wrapper, nor the accepted domain_ UUID alternative form encoded in the subscriptionId pattern.

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 verb and resource ("Returns one Lovie subscription") and enumerates what comes back: price, billing interval and interval_count, current period, and invoices. It also distinguishes itself from the list tool by requiring an id that list_subscriptions produced.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite workflow: "Never ask the user for the id; list subscriptions first," naming lovie_billing_list_subscriptions as the source. This is a clear when-to-use rule plus the alternative to call beforehand, leaving nothing to inference.

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.