Skip to main content
Glama

Lovie Company Formation

Get Billing Overview

lovie_billing_get_overview
Read-only

Summarizes what the company pays Lovie: the next charge, how many Lovie subscriptions are active or ending, the card on file (brand, last four digits and expiry), the billing profile Stripe bills (email, legal name, address, and a tax id's type and last four) and any payment that failed. Use it for 'what do we pay Lovie?' or 'did our Lovie payment go through?'. This is Lovie's billing of the company, not the company's own invoices to its customers. Changes to the card or a plan happen in Stripe; point the user to Settings > Billing.

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

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
alertNo
summaryNo
paymentMethodNo
billingDetailsNo
portalAvailableNo
viewerCanManageNo
stripeUnavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's read-only framing adds little there; however it adds real context the annotations do not cover — that mutations must happen in Stripe, that sensitive card data (brand, last four, expiry) and tax id fragments are returned, and that failed payments are surfaced. Pagination/limits are not mentioned, though the presence of an output schema reduces that burden.

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?

Three sentences, front-loaded with the core purpose, then enumeration of contents, then disambiguation and a redirect. The disambiguating sentence about invoices versus Lovie's billing genuinely earns its place because sibling tools cover company-side invoices.

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?

An output schema exists, so return values need not be described; for a read-only overview with one well-documented parameter this description is complete enough to call correctly and to explain the result to a user, including where to send them for changes.

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?

There is a single required parameter (a nested UUID value wrapper) with 100% schema description coverage, so the schema already carries the semantics. The description adds no information about what companyId means or how to obtain it, which is acceptable given full coverage but is not value beyond the schema.

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 (summarizes) and a precisely scoped resource (what the company pays Lovie), then enumerates the summary's contents: next charge, active/ending subscriptions, card on file, billing profile, failed payments. It also draws the boundary explicitly against the company's own customer invoices, which is what separates it from siblings like lovie_billing_list_invoices.

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 two literal trigger questions ('what do we pay Lovie?', 'did our Lovie payment go through?') plus a negative boundary (not the company's own invoices) and an explicit routing instruction: card/plan changes happen in Stripe via Settings > Billing. That is when-to-use, when-not-to-use, and where to go instead.

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.