Skip to main content
Glama

Lovie Company Formation

Recover Equity Subscription

equity_onboarding_get_payment_link
Destructive

Creates a Stripe subscription checkout or recovery link for the authenticated company's owner after company proof has been submitted. Ownership is checked by the backend, including for delegated agents. First read subscription access and the offered plans; confirm the company's name, quoted price and billing period with the owner. billing_interval is month or year; empty defaults to month. The server chooses the Price. return_app is only for the Mac app; agents must leave it empty. Changing period may expire the previous unpaid link. Existing outstanding subscriptions return an authenticated Lovie payment-page link for delegated agents, never a billing-portal credential or a second subscription. Return payment_url unchanged: new subscriptions open Stripe checkout; existing subscriptions open Lovie before the owner continues to Stripe. Never request card details or pay for them. A link is not payment confirmation: re-read subscription access afterward. Active or processing payments and uncertain status refuse another checkout.

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

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.
returnAppNo
billingIntervalNo

Output Schema

NameRequiredDescriptionDefault
paymentUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / returnApp
      Added value: +{
      +  "maxLength": 24,
      +  "pattern": "^(|co\\.lovie\\.macos|co\\.lovie\\.macos\\.staging|co\\.lovie\\.macos\\.dev)$",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare openWorldHint and destructiveHint; the description adds substantial context beyond them: the server picks the Price, changing the billing period may expire the previous unpaid link, existing subscriptions yield a Lovie payment-page link rather than credentials or a duplicate subscription, and links are not payment confirmation. The warning never to request or handle card details and the instruction to re-read access afterward are behaviors no schema or annotation conveys.

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 purpose and gating condition are front-loaded, and nearly every sentence carries a distinct operational rule. It is dense for a three-parameter tool, with parameter defaults (billing_interval, return_app) buried mid-paragraph rather than grouped, which slows scanning.

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?

For a multi-step, externally-facing flow with payment implications, the definition covers prerequisites, parameter constraints, link-kind differences, safety prohibitions, and post-call verification. An output schema exists, so return-value documentation is correctly left out, with only the actionable 'return payment_url unchanged' guidance included.

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?

Schema description coverage is 33% and only companyId carries a (tautological) description, so the description does the real work: it clarifies that billing_interval is month or year with empty defaulting to month, and that return_app is Mac-app-only and must be empty for agents. companyId's ownership semantics are covered by the backend-check note rather than by the parameter itself.

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?

The description opens with a specific verb and resource: 'Creates a Stripe subscription checkout or recovery link,' scoped to the authenticated company's owner and gated on company proof submission. That scope language distinguishes it from generic payment-link siblings such as formation_get_payment_link, since it only applies to the equity subscription flow.

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?

It prescribes a concrete pre-call sequence: read subscription access and offered plans first, then confirm company name, quoted price and billing period with the owner. It also states an exclusion ('agents must leave it empty' for return_app) and refusal conditions (active, processing, or uncertain payment status). It stops short of naming the alternative tools explicitly, leaving the agent to map 'read subscription access' to a sibling.

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.