Skip to main content
Glama

List room task templates

city_room_task_templates
Read-onlyIdempotent

List the built-in task templates (for example code review, bug triage, research question): id, version, name and purpose. Pass template_id here for one template in full (title prefix, body sections, acceptance criteria and the Markdown body it prefills), or pass the id as template_id to city_room_task_create.

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": "city_room_task_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
room_idNoIgnored: the catalog is the same everywhere.
agent_idNoIgnored.
template_idNoOne template in full (sections, criteria, body). Without it: the short list.

Output Schema

NameRequiredDescriptionDefault
templatesYes
catalog_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / template_id
      Added value: +{
      +  "description": "One template in full (sections, criteria, body). Without it: the short list.",
      +  "enum": [
      +    "code-review",
      +    "bug-triage",
      +    "research-question",
      +    "writing-draft",
      +    "launch-checklist",
      +    "test-plan"
      +  ],
      +  "type": "string"
      +}
    • removedOutput schema / properties / templates / items / additionalProperties
      Removed value: -false
    • addedOutput schema / properties / templates / items / anyOf
      Added value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "body": {
      +        "type": "string"
      +      },
      +      "criteria": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "purpose": {
      +        "type": "string"
      +      },
      +      "sections": {
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "heading": {
      +              "type": "string"
      +            },
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "heading",
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "title_prefix": {
      +        "type": "string"
      +      },
      +      "version": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "version",
      +      "name",
      +      "purpose",
      +      "title_prefix",
      +      "sections",
      +      "criteria",
      +      "body"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "purpose": {
      +        "type": "string"
      +      },
      +      "version": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "version",
      +      "name",
      +      "purpose"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties / templates / items / properties
      Removed value: -{
      -  "body": {
      -    "type": "string"
      -  },
      -  "criteria": {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  "id": {
      -    "type": "string"
      -  },
      -  "name": {
      -    "type": "string"
      -  },
      -  "purpose": {
      -    "type": "string"
      -  },
      -  "sections": {
      -    "items": {
      -      "additionalProperties": false,
      -      "properties": {
      -        "heading": {
      -          "type": "string"
      -        },
      -        "hint": {
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "heading",
      -        "hint"
      -      ],
      -      "type": "object"
      -    },
      -    "type": "array"
      -  },
      -  "title_prefix": {
      -    "type": "string"
      -  },
      -  "version": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / templates / items / required
      Removed value: -[
      -  "id",
      -  "version",
      -  "name",
      -  "purpose",
      -  "title_prefix",
      -  "sections",
      -  "criteria",
      -  "body"
      -]
    • removedOutput schema / properties / templates / items / type
      Removed value: -"object"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful context about the built-in nature of the templates and the shape of the full-template response, including sections, criteria, and prefilled body. It does not contradict the annotations.

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 two tight sentences with no wasted text. The primary list behavior is front-loaded, followed by the template_id detail and the create-tool alternative.

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?

Given the presence of annotations and an output schema, the description is largely complete for correct invocation: it explains the list mode, full-detail mode, and the create-tool handoff. The main remaining gap is not differentiating this catalog from the sibling city_list_templates.

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 room_id/agent_id as ignored and template_id as selecting one full template. The description mostly restates the template_id behavior and does not add much parameter meaning beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: listing built-in room task templates. It also explains the two modes, short list vs. full template, which helps the agent understand the tool's scope. It does not clearly distinguish itself from the sibling city_list_templates, so sibling differentiation is incomplete.

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?

It gives clear guidance on when to omit template_id (short list) and when to include it (one template in full). It also names city_room_task_create as the alternative for actually creating a task from a template. It does not address when to use this tool vs. city_list_templates.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.