Mitti MCP Server

Templates Get Template

templates_get_template

Retrieves summary metadata for a Mitti template by its ID, providing name, description, owner, archived status, and creation/update dates.

Instructions

Get summary metadata for a specific Mitti template by its ID. Returns name, description, owner, archived status, and dates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`template_id`	Yes	The unique template ID (starts with 'template_').

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Template name
`archived`	No	Whether this template is archived
`created_at`	No	Creation timestamp
`owner_name`	No	Template owner display name
`description`	No	Template description
`modified_at`	No	Last modification timestamp
`template_id`	Yes	Unique template identifier

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses that only summary metadata is returned and names the exact fields. The read-only nature is implied by 'Get summary metadata', though not explicitly stated.

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 tight sentences: the first states purpose and scope, the second lists return fields. No filler or redundant restatement of the name.

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?

For a single-parameter get-by-ID operation with an output schema, the description covers purpose, selection, and return contents. No additional context is needed 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?

Schema coverage is 100% and the schema already documents template_id, including the 'template_' prefix. The description only adds 'by its ID', which does not materially enrich parameter semantics beyond the baseline.

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?

The description uses a specific verb ('Get'), a clear resource ('summary metadata for a specific Mitti template'), and a selection criterion ('by its ID'). It also enumerates the returned fields, making it distinguishable from list and definition siblings.

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?

The description implies the tool is for retrieving one known template's summary metadata, but it does not explicitly state when to use this over templates_list_templates or templates_get_template_definition. There is no when-not or alternative guidance.

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

Deploy Server