Lovie Company Formation

Get Registered Agent

registeredagent_get_agent

Read-only

Returns the company's registered agent on record and whether Lovie can take the appointment over. When it cannot, the response names the one reason — say what the company would need instead rather than only refusing, and never quote the price alongside a refusal.

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

Input Schema

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

Output Schema

Name	Required	Description	Default
`agent`	No
`eligibility`	No
`renewalDate`	No
`termEndDate`	No
`moveAvailable`	No
`termStartDate`	No
`liveMoveRequestId`	No
`unavailableReason`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral context the annotations do not: the response contains a single named reason on failure, and there is a business rule against quoting price alongside a refusal. It omits any note on auth or permission requirements.

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?

Two sentences, front-loaded with what is returned, followed by a short handling rule. Every clause carries information; the second sentence is phrased as an instruction to the caller rather than a description, which is slightly unusual but not wasteful.

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?

With one fully documented parameter, an output schema, and complete read-only annotations, the description only needs to add the business framing, which it does. The refusal-handling rule is the key missing piece elsewhere and is supplied here.

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 one parameter (companyId) at 100% schema description coverage, and the schema handles the nested UUID wrapper. The description adds no meaning beyond the schema, so baseline 3 applies.

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 uses a specific verb and resource: it returns the company's registered agent on record plus an eligibility signal for whether Lovie can take over the appointment. That is clearly distinct from siblings like registeredagent_get_quote or registeredagent_get_request, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the lookup to run before offering a registered-agent takeover, and that it should be followed by registeredagent_get_quote when relevant. There is no explicit when-to-use or when-not-to-use statement naming an alternative tool.

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.