Skip to main content
Glama

List Carousel Board Templates

carousels_board_templates
Read-onlyIdempotent

List carousel slide templates: id, family, label and slots (key, kind text or image, sample). carousels_board_edit insertTemplateSlide takes a template id and slot values.

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

Input Schema

NameRequiredDescriptionDefault
workspaceIdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds useful detail beyond that: the shape of each template record and the slot model (key, kind text or image, sample), plus the downstream consumption pattern. It doesn't discuss ordering or whether the list is workspace-scoped, which keeps it from a 5.

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?

Two tight sentences with no filler; the core listing purpose and return shape are front-loaded. The phrasing is somewhat telegraphic ("slots (key, kind text or image, sample)"), but nothing is wasted.

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 an output schema present and full annotation coverage, the description only needs to explain purpose and relationships, which it does, including the link to insertTemplateSlide. The main remaining gap is the unexplained workspaceId scoping, which matters for a listing tool that may return global versus workspace-specific templates.

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

Parameters2/5

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

There is one optional workspaceId parameter with 0% schema description coverage, and the description never mentions it at all — not what it scopes, nor what a null value means. Because the schema provides no documentation, the description needed to compensate for that gap and does not.

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 opens with a specific verb+resource ("List carousel slide templates") and names the returned fields (id, family, label, slots), so the agent knows exactly what this tool produces. It falls short of a 5 because it doesn't contrast itself with nearby listing/sibling tools except by pointing at the consumer tool carousels_board_edit.

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?

The second sentence implicitly defines the workflow: fetch templates here to obtain a template id, then pass that id plus slot values to carousels_board_edit insertTemplateSlide. This is clear context for when to use it, but there are no explicit exclusions or statement of when not to call it.

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