get_templateGet a single template by ID
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Template ID (from list_templates) |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | The template — id, name, description, type, its pages, and the datasources it expects. | |
| success | Yes | True when the call succeeded. |
Changes observed during successful MCP inspections.
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / properties / success / descriptionPrevious value: -"True when the call succeeded. A failure comes back as an error result instead."New value: +"True when the call succeeded."Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": {},
+ "description": "The template — id, name, description, type, its pages, and the datasources it expects.",
+ "type": "object"
+ },
+ "success": {
+ "description": "True when the call succeeded. A failure comes back as an error result instead.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "success"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond the basic get operation—no error handling, permission requirements, or return format details. Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to repeat safety, but it also contributes no extra behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, unambiguous sentence with no unnecessary words. It is front-loaded with the key action and resource.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only getter with one parameter, an output schema, and readOnly annotations, the definition is nearly complete. The only minor gap is the absence of explicit guidance on sourcing the ID, though that is covered in the schema's parameter description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% because the id parameter is fully described ('Template ID (from list_templates)'). The description itself adds no parameter semantics, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get'), resource ('template'), and retrieval method ('by ID'), making the tool's function immediately clear. It also distinguishes itself from sibling tools like list_templates (which lists all templates) and update_template (which modifies one).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when/when-not guidance is provided in the description, but the parameter schema's note 'Template ID (from list_templates)' implies a workflow: first list templates to obtain an ID, then use this tool. The usage context is implied rather than explicitly stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.