Amiqus MCP server

List templates

list_templates

Read-onlyIdempotent

List record, email, or document templates from Amiqus, optionally filtered to enabled or disabled ones, with paging support.

Instructions

Templates on the team: record templates (the preset steps, notification, message, reminders and assignees a create_record from that template would use; GET /templates/records), email templates (GET /templates/emails) or document templates (GET /templates/documents). Optionally only enabled or only disabled ones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_templates"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Which template list	records
`page`	No	API page number to start from (1-based, as documented; use next_page from a previous call)
`enabled`	No	Only enabled (true) or only disabled (false) templates (API parameter `enabled`; both by default)
`max_results`	No	Most records to return in this call; whole API pages only (up to 100 per page), so fewer may come back with a next_page to continue from

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower; the description still adds real semantic value by explaining what a record template actually contains (preset steps, notification, message, reminders, assignees). It stops short of describing pagination behavior, which the schema covers instead.

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?

A single front-loaded sentence that names the resource first and then triages the kinds with endpoints. The nested parenthetical for record templates is dense but each clause carries information, so no trimming is obvious.

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 read-only listing tool with full schema coverage and no output schema, the description supplies the semantic context an agent needs to pick the right 'kind'. Nothing critical is missing, though it never says what the returned template objects look like or how they relate to create_record beyond the record case.

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 description coverage is 100%, so the baseline is 3; every parameter is already documented in the schema, including paging and max_results limits. The description only marginally enriches meaning by explaining that 'enabled' yields only enabled or only disabled lists, which the schema also states.

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+resource ('Templates on the team') and enumerates the three template kinds with their backing endpoints (GET /templates/records, /emails, /documents). An agent can immediately tell this apart from the sibling list_records/list_clients/list_webhooks tools.

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?

Usage is implied by the enumeration of kinds and the enabled/disabled scoping option, but there is no explicit guidance on when to choose this tool over list_records or get_record, nor any stated prerequisites. Adequate but leaves the agent to infer route selection.

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

Deploy Server