Skip to main content
Glama

Read carousel link

read_carousel_link
Read-onlyIdempotent

Turn a Slyd carousel link (…/app/new#s=… or #j=…) back into its JSON spec, so it can be revised and passed to create_carousel for a new link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "read_carousel_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe Slyd link the user shared.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so safety and determinism are covered without description help. The description adds that the URL is decoded into a spec rather than merely fetched, but says nothing about failure behavior for malformed or non-Slyd links, which is the main remaining unknown.

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?

One front-loaded sentence that carries the transformation, the accepted input formats, and the downstream consumer. Nothing is redundant or padded.

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 one-parameter, read-only tool with no output schema, the description conveys enough: what comes in, what comes out (the JSON spec), and what to do with the result. The only omission is what happens when the link is invalid or not a Slyd link.

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%, so the baseline is 3, but the description genuinely adds meaning by enumerating the acceptable link shapes (#s=… or #j=…) that the single 'url' parameter must contain, going beyond the schema's generic 'The Slyd link the user shared'.

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 states a specific verb+resource+transformation: it turns a Slyd carousel link back into its JSON spec. It even names the accepted link forms (…/app/new#s=… or #j=…), which lets an agent tell instantly that this is the inverse of create_carousel rather than another creation or lookup tool.

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?

Usage context is clear: use it when you have an existing shared link and need to revise it before passing the result to create_carousel. There is no explicit exclusion or 'use X instead' clause, but the round-trip workflow it belongs to is unambiguous.

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