Mitti MCP Server

Actions Get Action

actions_get_action

Retrieve full details for a Mitti action by its unique ID, including title, description, status, priority, due date, assignees, and site.

Instructions

Get full details of a specific Mitti action by its ID. Returns title, description, status, priority_id, due date, assignees, and site.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action_id`	Yes	The unique action ID.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Unique action identifier
`title`	Yes	Action title
`due_at`	No	Due date/time
`status`	No	Action status: 'open', 'in_progress', 'completed', 'cant_do'
`site_id`	No	Site this action belongs to
`assignees`	No	List of assignee user IDs
`created_at`	No	When the action was created
`description`	No	Detailed description
`modified_at`	No	Last modification timestamp
`priority_id`	No	Org-specific priority identifier (Mitti's task-type system uses UUIDs, not fixed 'low'/'medium'/'high' labels — this field is not human-readable)
`creator_user_id`	No	User ID who created the action

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 15, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. 'Get' implies a read-only operation and the returned fields are listed, but there is no explicit statement about not-found behavior, authentication needs, or side effects. It adds some context but leaves behavioral gaps.

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

Conciseness5/5

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

Two focused sentences with no filler. The core purpose is front-loaded, and the field list earns its place by setting expectations about what 'full details' means.

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?

For a simple single-parameter get operation with an output schema available, the description plus schema is nearly complete. It could mention error handling or authorization, but nothing essential is missing for correct invocation.

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

Parameters3/5

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

The input schema covers 100% of parameters and already describes action_id as 'The unique action ID.' The description only reinforces 'by its ID' without adding format, source, or usage nuances, so baseline 3 is appropriate.

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 ('Get'), a specific resource ('full details of a specific Mitti action by its ID'), and lists the returned fields. This clearly distinguishes it from sibling actions_list_actions, which lists actions rather than retrieving one.

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?

The phrase 'by its ID' makes the usage context clear: call this when you already have an action_id and need full details for that single action. It does not explicitly name alternatives or exclusions, but the intended trigger is obvious.

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

Deploy Server