Skip to main content
Glama

Carousel guide

get_carousel_guide
Read-onlyIdempotent

Everything needed to write a great Slyd carousel: copywriting rules, every slide layout and its fields, templates, palettes, fonts, textures, backgrounds, icons, freeform element coordinates, and a complete example. Useful before a first carousel.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and repeatability are covered. The description adds value by inventorying the guide's contents, but it says nothing about the return format (structured data vs. prose) or the guide's size, which matters for an agent budgeting context.

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 front-loaded sentence with the purpose first and the content inventory after; every listed item conveys what the guide contains. The comma-separated list is long but each entry earns its place as a coverage claim.

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?

For a zero-parameter, read-only retrieval tool with no output schema, the description is nearly complete — it says what the guide covers. The remaining gap is how the content is delivered (format, length), which an agent would want to know before pulling it into context.

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 nothing for the description to disambiguate; the baseline applies. The enumeration of covered topics is a reasonable substitute for parameter detail.

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 specific resource — a Slyd carousel authoring guide — and enumerates its contents (copywriting rules, slide layouts, palettes, fonts, example), so the agent knows exactly what this returns. It is clearly a reference tool distinct from the sibling create_carousel, though it never states that contrast explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Useful before a first carousel" gives an implied usage cue, but it is hedged and passive. There is no explicit when-to-use/when-not, no mention that it should be consulted prior to create_carousel, and no guidance on whether it is needed for subsequent carousels.

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