Lovie Company Formation

Get Move Quote

registeredagent_get_quote

Read-only

Returns Lovie's price and term for becoming a Wyoming company's registered agent. One all-inclusive amount. Quote the exclusions with it: being the agent means receiving service of process and state mail, and nothing beyond that.

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

Input Schema

Name	Required	Description	Default
`companyId`	Yes	UUID value wrapper.

Output Schema

Name	Required	Description	Default
`price`	No
`coverage`	No
`currency`	No
`exclusions`	No
`termMonths`	No
`typicalBusinessDays`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already establish read-only, non-destructive, closed-world behavior, and the description adds meaningful quote-specific context: one all-inclusive amount and the precise exclusions of receiving service of process and state mail only. It does not cover permissions or error behavior, but with annotations and an output schema that gap is modest.

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?

The description is front-loaded with the return value, then a short qualifier, then the exclusion instruction; every sentence contributes. There is no redundant restatement of the tool name or schema.

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?

For a one-parameter read-only quote tool with annotations and an output schema, the description gives enough content about what the quote includes and excludes. Minor gaps remain around companyId preconditions and the title's 'Move Quote' wording, but the callable behavior is covered.

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% for the single companyId parameter, so the schema already carries its semantics. The description does not add format, constraints, or additional meaning for companyId beyond that baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it returns Lovie's price and term for becoming a Wyoming company's registered agent, with an all-inclusive amount. It does not explicitly distinguish this quote tool from nearby quote or registered-agent tools such as formation_get_formation_quote or formation_purchase_registered_agent, so it misses the sibling-differentiation bar for a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The instruction to quote the exclusions tells the agent how to present the result, not when this quote tool should be selected over formation or purchase tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lovie Company Formation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.