Skip to main content
Glama

Lovie Company Formation

Get Equity Subscription Access

equity_onboarding_get_subscription_access
Read-only

Reads company setup and current equity subscription access from Stripe for a company reader. Read this before cap-table work and after the person returns from paying. Complete company proof before requesting a payment link. Where payment_required is true, continue cap-table work only when setup_complete and subscription_active are true. A link, paid_at receipt, or the person's claim of payment never proves current access. Errors mean access could not be checked; never treat them as paid or free.

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

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
setupStartedNo
canChoosePlanNo
setupCompleteNo
detailsCompleteNo
paymentRequiredNo
subscriptionStateNo
subscriptionActiveNo

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 establish readOnly/openWorld/non-destructive, but the description adds real behavioral context beyond them: the read hits an external system (Stripe), the response carries payment_required/setup_complete/subscription_active gate flags, and errors mean 'access could not be checked' rather than a paid/free verdict. It does not describe rate limits or caching/freshness of the Stripe read, which keeps it short of a 5.

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?

Five short sentences, front-loaded with what is read and followed by gating rules; each sentence carries distinct decision logic rather than restating the name. Slight density in the 'link, paid_at receipt, claim' sentence and the following error sentence, which overlap thematically, but nothing is redundant 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?

With an output schema present the description need not explain return fields, and it compensates by explaining the failure interpretation (errors are not evidence of access) and the gating semantics that an agent must apply. For a one-parameter, read-only gating check, an agent has everything needed to call it and act on the result correctly.

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 100% with a single required companyId UUID wrapper, so the schema already does the documenting work. The description's reference to 'a company reader' loosely reinforces that the call is company-scoped but adds no syntax or format detail beyond the schema, which is the expected baseline-3 case for full coverage.

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 names a specific verb (reads) and a specific resource pair (company setup state and current equity subscription access), plus the source system (Stripe). It is clearly distinguishable from the nearby get_payment_link and generic equity_onboarding_get siblings by scoping itself to access/subscription state for a company reader.

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?

It gives explicit placement in a workflow (before cap-table work, after the person returns from paying, before requesting a payment link) and explicit exclusions (a payment link, paid_at receipt, or the person's claim is never proof of access). The condition for proceeding (setup_complete AND subscription_active true when payment_required is true) removes ambiguity about when to continue.

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.