Mitti MCP Server

Inspections List Inspections

inspections_list_inspections

List inspections from Mitti with optional template and modification date filters. Returns audit IDs, template IDs, and timestamps for each inspection, enabling follow-up retrieval of full details.

Instructions

List inspections from the Mitti (formerly SafetyCulture) account. Supports filtering by modification date and limiting the number of results. Returns only audit_id, template_id, and modification date per inspection — the search API does not return name, owner, score, or status. Call get_inspection with a specific audit_id for full details.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of inspections to return (1–100, default 20).
`template_id`	No	Filter by a specific template ID.
`modified_after`	No	ISO 8601 timestamp — only return inspections modified after this time. Example: '2024-01-01T00:00:00.000Z'

Output Schema

TableJSON Schema

Name	Required	Description
`total`	No	Total number of matching inspections (may exceed page size)
`inspections`	No
`next_page_token`	No	Cursor for the next page of results

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the burden of disclosure. It clearly states a key behavioral trait: only audit_id, template_id, and modification date are returned, and the search API does not return name, owner, score, or status. It implies read-only behavior by saying 'list', although it does not cover rate limits or authentication detail.

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?

The description is three sentences, each serving a distinct purpose: statement of purpose, supportable capabilities, and a field limitation with an alternative call. There is no fillable extra text or irrelevant detail; every sentence is front-loaded and adds value.

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?

The presence of an output schema means return values do not need full explanation; the description still covers the critical limitations and directs the agent to a richer tool. It does not mention the sibling 'inspections_list_inspections_view', which could cause mild ambiguity, but the overall context is sufficient for guided use.

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 all three parameters with 100% description coverage, so the schema already explains limit, template_id, and modified_after. The description repeats the 'modification date' and 'limiting' concepts but adds no new parameter-level semantics beyond what the schema provides.

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 states the specific verb and resource ('List inspections from the Mitti account') and explicitly differentiates this tool from get_inspection by saying 'Call get_inspection with a specific audit_id for full details.' It also communicates the limited field set, which helps distinguish it from a fuller inspection tool.

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?

It explicitly tells the agent when to use get_inspection instead ('Call get_inspection with a specific audit_id for full details'), serving as a clear alternative. It also describes the general filtering and limiting capabilities, giving a sense of when the tool is appropriate.

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

Deploy Server