sentarion-mcp

recall_and_replan

Recall prior state from both execution chains and generate a new plan, enabling resumption of multi-agent orchestration with full context.

Instructions

Recall prior state from both chains, feed it into a new Algernon plan.

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": {
      "query": "<query>",
      "k": "<k>"
    },
    "name": "recall_and_replan"
  }
}

Input Schema

Name	Required	Description	Default
`k`	Yes
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Aug 31, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states that prior state is recalled and fed into a new plan, but it does not disclose whether this modifies or replaces anything, whether it is a read-only operation, what side effects occur, or what the output looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler and the primary action comes first, which is efficient. However, it relies on unexplained domain jargon and is so brief that it sacrifices clarity, making it only adequate structure-wise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description communicates the basic operation but is far from complete for a tool with two required parameters, no output schema, and no annotations. It lacks parameter mapping, expected inputs, output behavior, and prerequisites, leaving an agent without enough information to invoke the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the two required parameters, query and k. It does not mention either parameter at all. An agent cannot determine what values to pass, especially k, which has no reasonable default meaning from its name or the description.

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, 'Recall', with a clear resource, 'prior state from both chains', and an action, 'feed it into a new Algernon plan'. It is not a tautology and conveys a distinct recall-and-replan purpose, though terms like 'both chains' and 'Algernon plan' are unexplained.

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?

No guidance is given about when to use this tool versus sibling tools such as recall, remember, govern, or orchestrate_and_record. The intended use is only implied by the description, not stated, and there are no exclusion conditions or alternatives mentioned.

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

Deploy Server