Skip to main content
Glama

List templates, layouts and themes

catalog
Read-only

List presentation templates, slide layouts, color themes, and the default house style before building a deck. Call this first to see available text fields and icon slots per layout.

Instructions

Lists the presentation templates, slide layouts (with the text fields and icon slots each one has), color themes and the house style (the default look). Call this first.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the substantive behavioral detail that the result includes each layout's text fields and icon slots and the default house style. It does not describe the response shape in detail, but as a zero-parameter read that gap is minor.

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 sentences with zero filler: the first front-loads the full inventory of returned items, and the second is a single imperative action cue. Nothing is redundant with the title or annotations.

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?

With no input parameters and no output schema, the description carries the burden of explaining returns, and it does so by naming all four asset categories plus the nested detail inside layouts. For a simple discovery tool, nothing an agent needs in order to call it correctly is missing.

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 no parameters, so the baseline is 4 and there is nothing for the description to compensate for. The description correctly implies a no-argument, whole-catalog call without inventing filtering options that the schema does not support.

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 opens with a specific verb ('Lists') and enumerates exactly what is returned: presentation templates, slide layouts with their text fields and icon slots, color themes, and the house style. The parentheticals disambiguate 'layouts' and 'house style', so an agent knows this is a catalog of design assets rather than a sibling like list_fonts or get_presentation.

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?

'Call this first' gives an explicit ordering cue that tells the agent when to reach for this tool relative to its siblings. It stops short of naming alternatives, exclusions, or what to do after the catalog is retrieved, so it falls just short of the top band.

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