Skip to main content
Glama
Sign In

SwiftProbate

by com.swiftprobate
OverviewDiscussionsAdmin

update_task_status

Destructive

Update a task's status. Use this when the user asks to mark a task as completed, in progress, etc. Marking a task completed or not_applicable (not required) is the customer's decision: only do it when they have said so, and pass their words in customer_words. To restore a task marked not required, set it back to not_started.

Input Schema

NameRequiredDescriptionDefault
statusYesThe new status
task_idYesThe task ID to update
estate_idYesThe estate to act on. Call list_my_estates first to get this id.
customer_wordsNoRequired when marking a task completed or not_applicable, or setting bypasses_probate or has_beneficiary to true: the customer's own words stating that decision, quoted exactly from their message (e.g. "mark this not required", "I paid the filing fee", "it's payable on death to my brother"). Never your own conclusion. If they haven't stated the decision, don't call — ask them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / customer_words
      Added value: +{
+  "description": "Required when marking a task completed or not_applicable, or setting bypasses_probate or has_beneficiary to true: the customer's own words stating that decision, quoted exactly from their message (e.g. \"mark this not required\", \"I paid the filing fee\", \"it's payable on death to my brother\"). Never your own conclusion. If they haven't stated the decision, don't call — ask them.",
+  "type": "string"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the consent policy: completing or marking not required is the customer's decision, requires quoted customer_words, and the agent must ask rather than infer. It does not mention reversibility or consequences of a mistaken update, which matters given destructiveHint=true.

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?

Three front-loaded sentences with no filler; the core action comes first, followed by the consent rule and the recovery case. Slightly dense but every sentence earns its place.

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?

Covers the non-obvious hazards (acting without consent, restoring a not-required task) for a 4-parameter mutation tool with no output schema. Missing only the standard mutation caveats such as reversibility and audit side effects implied by destructiveHint=true.

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 baseline is 3; the description adds real meaning by framing customer_words as a policy gate rather than a free-text field and by explaining the not_applicable -> not_started transition. It still doesn't clarify estate_id lookup or the semantics of the other two enum values.

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+resource ("Update a task's status") that is immediately distinguishable from edit_task, update_task_deadline and update_task_notes. It does not explicitly name those siblings, so it stops short of 5.

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 concrete triggering conditions ("when the user asks to mark a task as completed, in progress, etc.") plus a restore path for not_applicable -> not_started. It never names the alternative sibling tools, so routing among update_variants is left implicit.

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

All SwiftProbate toolsInspect
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.

Resources