Skip to main content
Glama

Lovie Company Formation

Get Equity Onboarding Fee

equity_onboarding_get_fee
Read-only

Quotes the equity subscription plans for a company's cap table. Read-only. When required is false there is no fee in this environment and nothing to collect. Company intake can finish without payment. paid only records that a payment was once confirmed; it never proves current access, so read equity_onboarding_get_subscription_access for that. Read the offered plans before asking the owner to choose a billing period, then use equity_onboarding_get_payment_link to return a Stripe link. Never ask for card details or claim that quoting a plan pays it.

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": {
      "onboardingId": "<onboardingId>"
    },
    "name": "equity_onboarding_get_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
onboardingIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
paidNo
plansNo
currencyNo
requiredNo
unitAmountNo
productNameNo
recurringIntervalNo
recurringIntervalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds real operational context beyond them: the required=false no-fee path, the warning that 'paid' records a past confirmation and never proves current access, and explicit prohibitions (never ask for card details, never claim quoting a plan pays it). That is exactly the kind of side-effect and misuse guidance annotations cannot carry.

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?

Purpose is front-loaded in the first sentence, with flow and warnings following in a logical order. It is dense with short imperative clauses and slightly sprawling, but nearly every sentence either routes to a sibling or prevents a specific misuse, so little is wasted.

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 read-only quoting tool with an output schema, the description supplies the prerequisites, the no-fee branch, the downstream payment step, and the access-status alternative. Nothing an agent needs in order to call and interpret it correctly is missing, other than the parameter shape already covered by the schema.

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% and there is a single required onboardingId, so the schema already documents the parameter; the description never mentions it, including the nested UUID value wrapper. Baseline 3 applies because the schema does the heavy lifting.

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: "Quotes the equity subscription plans for a company's cap table." It also implicitly contrasts with equity_onboarding_get_subscription_access (access status) and equity_onboarding_get_payment_link (payment), so an agent can place it among siblings without opening a schema.

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?

Explicit sequencing is given: read the offered plans before asking the owner to choose a billing period, then call equity_onboarding_get_payment_link to return a Stripe link, and use equity_onboarding_get_subscription_access for current access. It also states the when-not case: when required is false there is no fee and company intake can finish without payment.

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.