Skip to main content
Glama

Get details for one PugSoda template

get_template
Read-onlyIdempotent

Get full details for a PugSoda template by slug: what photo to upload, clip duration, pricing, whether a free first-frame preview is shown before payment, step-by-step instructions, FAQ, and the direct upload URL.

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": {
      "slug": "<slug>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTemplate slug, e.g. "hit-the-road-dude", "clapping-cat", or "wild-west-saloon".

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful content context (that it reveals whether a free first-frame preview precedes payment, plus the direct upload URL), but says nothing about error behavior for unknown slugs or caching/staleness of pricing.

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?

Front-loaded with the verb and resource, then a compact enumeration of returned fields — no filler or restatement of the title. It is one dense run-on sentence, which is efficient but slightly harder to scan than a short listed form.

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, the description carries responsibility for describing the response and does so thoroughly via its field enumeration. Complete enough to call correctly; only missing edge-case guidance (unknown slug, deprecated templates) keeps it from a 5.

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

Parameters3/5

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

Schema coverage is 100% and the single `slug` parameter is fully documented in the schema with length bounds and concrete examples. The description only restates 'by slug', confirming rather than adding meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ('Get full details for a PugSoda template by slug') and enumerates exactly what those details include — upload photo, clip duration, pricing, preview behavior, instructions, FAQ, upload URL. An agent can tell it apart from list_trending_memes and search_templates because it is a single-slug detail lookup, though it never names those siblings.

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?

Gives clear context for use: you must have a slug, and this is the call that returns the full template record. It does not state the natural routing rule (find a slug via search_templates first) or what happens with an invalid slug, so it stops short of explicit when-to-use/when-not guidance.

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.