Lovie Company Formation

Get Move Request

registeredagent_get_request

Read-only

Returns one registered-agent move: where it stands, each version of the form, and what the state has said. Get the id from registeredagent_list_requests.

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": {
      "moveRequestId": "<moveRequestId>"
    },
    "name": "registeredagent_get_request"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
`packets`	No
`moveRequest`	No
`stateResponses`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare this is a read-only, non-destructive, closed-world operation. The description adds a summary of what is returned, but it does not add behavioral context such as error behavior, permissions, pagination, or state constraints. With annotations and an output schema already covering safety and return shape, this is a modest addition.

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?

Two compact sentences with no wasted wording. The core purpose is front-loaded, and the prerequisite for the ID is placed immediately after the return summary.

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 single-parameter read-only tool with annotations and an output schema, the description is nearly complete: it states the resource, outlines the return, and explains the ID source. A small gap remains around what a 'move' means or any retrieval constraints, but nothing essential is missing for correct invocation.

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 coverage is 100%, so the UUID shape is already documented. The description adds meaning beyond the schema by telling the agent where to obtain the moveRequestId, namely from registeredagent_list_requests.

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 uses a specific verb and resource: it returns one registered-agent move. It also previews the returned content (status, each form version, state commentary) and distinguishes itself from the list tool by saying the ID comes from registeredagent_list_requests.

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 gives a clear operational cue: get the ID from registeredagent_list_requests. That tells the agent when to use this tool and how to obtain the required input. It does not explicitly state exclusions or when not to use it, so it falls short of a full when/when-not treatment.

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.