Skip to main content
Glama

show_estate_setup

Read-onlyIdempotent

Show the signed-in user a short form, right in the chat, for setting up their estate in SwiftProbate. Submitting it builds their personalized probate checklist (the same as complete_onboarding, without asking the questions one by one). Use this when the user agrees to set up an estate, for example after list_my_estates shows they have none, or when they ask for help with their own situation (what to do for a specific person's estate, their next steps as executor) and have no estate yet. Do not use it for general probate questions, which the reference tools answer, or when the user already has an estate set up (use get_tasks instead). The result says whether the user has agreed to SwiftProbate's Terms on the website and whether an estate is already set up; the form shows the right screen for each case. If the form can't be shown in this chat, ask the setup questions conversationally and call complete_onboarding instead. SwiftProbate is software that helps people organize the probate process; it is not a law firm and does not give legal advice.

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": "show_estate_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: what the returned result conveys (Terms acceptance on the website, whether an estate already exists), that the form branches its screen accordingly, and a fallback path of asking the questions conversationally and calling complete_onboarding. The only minor blur is that 'submitting it builds their checklist' describes a consequence inside the form flow rather than the tool call, which slightly muddies the read-only framing, though it does not contradict it.

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?

Front-loaded with purpose, then usage, then result behavior, then the fallback, then a disclaimer — a sensible ordering with no filler in the core. The trailing 'not a law firm / no legal advice' sentence is somewhat boilerplate, but it plausibly shapes how the agent frames the interaction, so the length is defensible.

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

Completeness5/5

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

With no parameters and no output schema, the description must carry the contract, and it does: it explains the result fields, the screen-branching logic, and what to do when the form cannot be rendered. Nothing an agent needs in order to select or call this tool is missing.

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?

The tool takes zero parameters, so the baseline is 4 and there is no schema content to add to. The description usefully implies the form itself collects the setup inputs, so no argument-level detail is needed.

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?

Opens with a specific verb and resource: it shows a short setup form in-chat for creating an estate in SwiftProbate. It immediately distinguishes itself from complete_onboarding (same outcome, without asking questions one by one) and later from get_tasks and the reference tools, so an agent can place it without opening any schema.

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

Usage Guidelines5/5

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

Gives positive triggers (user agrees to set up an estate, list_my_estates returned none, user asks for help with their own executor next steps and has no estate) and explicit exclusions (general probate questions go to the reference tools; existing estate goes to get_tasks). Alternatives are named by name with the selecting condition.

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