Skip to main content
Glama

list_templates

Read-only

List public templates.

Anyone can read. filter='mine' restricts to the caller's templates. Archived templates are excluded unless include_archived is set, and even then only the caller's own archived templates are returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return in one page (1 to 200).
cursorNoPagination cursor from a previous response's next_cursor; omit to start from the first page.
filterNoWhich templates to return: 'mine' (you own) or 'all' public templates.all
searchNoCase-insensitive substring filter over name, description, and tags.
include_archivedNoWhen true, the caller's own archived templates are included alongside live ones. Archived templates belonging to other owners are never surfaced. Anonymous callers and non-owners always see only live templates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / filter / description
      Previous value: -"'mine' | 'all'"New value: +"Which templates to return: 'mine' (you own) or 'all' public templates."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark readOnlyHint=true, so description adds value by specifying that archived templates are excluded unless include_archived is set, and only own archived are returned. No contradictions.

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?

Two concise sentences, front-loaded with main purpose. Every sentence adds value; no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers key aspects: visibility, filtering, archived behavior. With complete schema, annotations, and output schema, description is sufficient for correct invocation.

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?

Schema coverage is 100%, but description adds meaningful context for filter and include_archived parameters beyond the schema. Explains behavior of 'mine' filter and archived inclusion.

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?

Clearly states 'List public templates' with a specific verb and resource. Distinguishes from sibling 'search_templates' by focusing on basic listing with filters.

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?

Provides clear contexts: 'Anyone can read', 'filter='mine' restricts to own templates', and archived behavior. Lacks explicit exclusion of when to use search_templates instead, but still guides usage well.

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.