Skip to main content
Glama

Antevo Wealth

Run succession rehearsal

run_succession_rehearsal
Read-onlyIdempotent

A rehearsal of the first thirty days if the principal could not act, tested against what is recorded today. Three stages (Day 1: who is called; Week 1: what can be reached; Day 30: what can be paid), each step ready, blocked, not confirmed or not recorded, with what is missing. Blocked means Antevo can see the gap. Not confirmed means a checklist item nobody has ticked yet: ask the person which of those are in place, and pass on next_step, which says where they tick them. Counts and roles only, never a name or an account number. It tests the file, not the law, and it does not compare cash with costs yet. Nothing is stored. Read only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_succession_rehearsal"
  }
}

Input Schema

NameRequiredDescriptionDefault
household_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, yet the description adds real context: output is counts and roles only, never a name or account number; nothing is stored; it tests the file and not the law; it does not compare cash with costs yet. These scope and privacy limits materially shape how the agent interprets and relays results. The closing 'Nothing is stored. Read only.' restates the annotations rather than adding to them.

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?

Purpose is front-loaded in the first sentence and every subsequent clause carries substance (stage breakdown, status definitions, privacy limit, scope limits). The prose is dense and comma-spliced, and the trailing 'Nothing is stored. Read only.' duplicates the annotations, but there is little true padding.

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 explained, and the description compensates by defining the four step statuses and the intended follow-up for unconfirmed items. What is missing is the only input: the meaning and optionality of household_id. With that added, the definition would be complete for a one-parameter read tool.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter household_id, which also carries a default of empty string, so the description carries the full burden. It never mentions household_id, what it identifies, or what an omitted/empty value scopes the rehearsal to. That is a substantive gap for an otherwise detailed definition.

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 opening states a specific verb and resource: a rehearsal of the first thirty days if the principal could not act, tested against the file as recorded today, broken into Day 1 / Week 1 / Day 30 stages. An agent knows exactly what it gets. It never names or contrasts itself with the sibling succession tools (get_succession_readiness, get_succession_checklist), so it stops short of 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 Guidelines3/5

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

There is useful post-call guidance: for items marked 'not confirmed', ask the person which are in place and pass on next_step. But there is no guidance on when to choose this over get_succession_readiness or get_succession_checklist, and no prerequisites (e.g., whether a household must exist first). Usage is implied by the scenario narrative rather than stated.

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.

Resources