Skip to main content
Glama

List templates

list_templates
Read-onlyIdempotent

Use this when the person asks to see templates or to change how the resume looks. Returns template ids with their format, columns, the roles each suits, and the colour ids. Works signed out.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact, 'Works signed out', which tells the agent no auth is required. Beyond that it only describes the return payload, so with annotations doing most of the work a 3 is right.

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?

Three short sentences, each doing a distinct job: selection trigger first, return shape second, auth constraint last. Nothing is repeated from the schema or annotations, and nothing could be cut without losing information.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so by naming the fields returned. Combined with the auth note and the selection trigger, an agent has enough to call it correctly. A minor gap is that it does not say whether templates are a fixed catalog or paginated, though for a no-arg listing this is small.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; the baseline of 4 applies. The description spends its space instead on return fields, which is the appropriate use of text for a no-arg tool.

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 gives a specific verb and resource ('list templates' implied by 'see templates') and enumerates exactly what is returned: template ids, format, columns, suited roles, and colour ids. The phrase 'to change how the resume looks' implicitly separates it from list_resumes, so an agent can tell these apart without inspecting the schemas.

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 supplies a concrete intent-based trigger: 'Use this when the person asks to see templates or to change how the resume looks.' That is clear guidance for selection. It stops short of naming alternatives or stating when not to use it, which keeps it below a 5.

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.

Resources