Skip to main content
Glama

show_my_tasks

Read-onlyIdempotent

Show the signed-in user's next open tasks for one estate as a card in the chat: the same Up Next list their SwiftProbate dashboard shows, up to five tasks with due dates, which ones are overdue, and which are waiting on another task. Users who can edit the estate can tick a task to mark it done, and can tap Ask about this to get help with a task. Use this when the user asks what's next, what they should work on, or to see or check off their tasks, and they already have an estate set up. It needs an estate_id from list_my_estates; if they have more than one estate and haven't said which, ask. Do not use it to search tasks, filter by status or asset, or read a task's full details (use get_tasks or get_task_detail), or when the user has no estate yet (offer setup instead). The result lists the tasks shown, the total number of open tasks, and whether the user can edit. If the card can't be shown in this chat, summarize the tasks from the result instead. SwiftProbate is software that helps people organize the probate process; tasks are general guidance, not legal advice.

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": {
      "estate_id": "<estate_id>"
    },
    "name": "show_my_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
estate_idYesThe estate to act on. Call list_my_estates first to get this id.

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?

Adds substantial behavior beyond the annotations: what the card renders, that edit permission gates the tick-to-complete affordance, what the result contains (tasks shown, total open count, edit flag), and a fallback to summarizing from the result if the card cannot render. One ambiguity remains: the description mentions ticking tasks done and asking about a task while annotations declare readOnlyHint=true, and it doesn't clarify whether those actions are executed by this tool or by a separate call — not a direct contradiction, but worth resolving.

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?

Long but front-loaded: purpose first, then usage triggers, then exclusions, then return shape. Most sentences carry routing weight; the closing framing sentence about SwiftProbate and non-legal-advice is useful context but not selection-relevant, which keeps it from a 5.

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 output schema, the description steps in to describe the result (tasks listed, total open count, edit permission) plus the card-vs-summary fallback. For a single-parameter, non-destructive display tool, an agent has everything needed to call it and interpret the response.

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% and the schema already tells the agent to call list_my_estates first, so the baseline applies; the description nonetheless adds disambiguation guidance (if the user has multiple estates and hasn't said which, ask) that the schema does not cover.

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?

States a specific verb and resource — "show the signed-in user's next open tasks for one estate as a card in the chat" — and pins down scope (up to five tasks, due dates, overdue, waiting-on-other-task). It explicitly distinguishes itself from get_tasks and get_task_detail, so an agent can route without opening schemas.

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 explicit triggers ("what's next", "what they should work on", see or check off tasks), a precondition (user already has an estate set up), a routing rule (estate_id from list_my_estates; ask if multiple estates and unspecified), and exclusions (not for searching, filtering by status or asset, or reading full task details; not when no estate exists — offer setup instead).

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