Skip to main content
Glama

Lovie Company Formation

Get Next Action

registeredagent_get_next_action
Read-only

Returns the single thing the user has to do next on their registered-agent move, already worded for them. Use it to answer 'what's the hold-up' without walking the whole request. An empty task is a normal answer: most of a move's life is Lovie's turn.

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

Input Schema

NameRequiredDescriptionDefault
moveRequestIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
taskNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a safe read. The description adds genuinely non-obvious behavior: the result is a single pre-worded task, and an empty task is a normal, expected answer because most of a move's life is the provider's turn. That prevents an agent from misreading an empty response as a failure.

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?

Three short sentences, front-loaded with what is returned, then usage, then the edge-case caveat. No filler and nothing repeated from the schema or annotations.

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?

An output schema exists, so return shape need not be described. The description covers the one behavior an agent could get wrong (empty result) for a simple single-parameter read tool. Only the 'Lovie' reference and the absence of any pointer to sibling read tools leave small gaps.

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% and the nested UUID wrapper is documented, so the schema carries the load. The description only hints at the parameter by calling it a 'registered-agent move' and never names moveRequestId or its format; baseline 3 is appropriate.

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?

States a specific verb and resource: returns the single next action on a registered-agent move, pre-worded for the user. It implicitly distinguishes itself from the heavier 'walk the whole request' path (registeredagent_get_request), though the internal term 'Lovie's turn' assumes product context an outside agent won't have.

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?

Gives a concrete use case ('what's the hold-up') and the alternative it replaces (inspecting the full request). It stops short of an explicit when-not, e.g. that this is not for auditing history or listing all open items, which lives in registeredagent_list_requests.

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.