Skip to main content
Glama

List graphic templates

list_graphics
Read-only

The animated graphic templates (yield trap, timeline, worked sum, stat card, formula card, two-line chart, lower third): what each shows, when to use it, its placements, and its data as JSON Schema with an example. Start here before preview_graphic and add_graphic.

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_graphics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's added burden is modest. It does contribute real value by disclosing the shape of the response — per-template usage notes, placements, and JSON Schema with an example — which matters because there is no output schema. It says nothing about size, ordering, or caching of the catalog.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence plus a short imperative routing line, with the 'start here' guidance front-loaded at the end where it is most actionable. The parenthetical list of seven template names is long but earns its place by telling the agent exactly what catalogue content to expect.

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?

With no output schema and no parameters, the description carries the return-value burden and does so adequately: it enumerates the template families and states the four attributes returned for each. It could be more complete by mentioning that the returned JSON Schema is directly consumable by add_graphic, but the essential picture is there.

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 per the baseline this scores 4. The description correctly implies a parameterless, whole-catalog read rather than suggesting any filtering option, which prevents the agent from inventing arguments.

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 names the resource specifically and even enumerates the seven template families (yield trap, timeline, worked sum, stat card, formula card, two-line chart, lower third), then states the per-template payload: what it shows, when to use it, placements, and data schema. The implicit verb is 'list/return a catalog' rather than a stated action verb, but the content scope is unambiguous and clearly distinct from preview_graphic or add_graphic.

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 an explicit sequencing rule: 'Start here before preview_graphic and add_graphic,' which tells the agent this is the discovery entry point and names the two tools it gates. It stops short of stating exclusions (e.g., when not to list, or whether to use suggest_graphics instead), so it is strong but not fully exhaustive.

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