Skip to main content
Glama

Memeoki

Caption a template

caption_template
Read-onlyIdempotent

Put your own exact words on one classic template. Instant, no AI involved. Use search_templates first to get the template id and its caption slots. captions can be an object (slot -> text) or a list of strings in slot order. Example: template "drake", captions ["Writing tests", "Shipping on Friday"].

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": {
      "template": "<template>",
      "captions": "<captions>"
    },
    "name": "caption_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
previewNoInclude the meme as an inline image
captionsYesslot -> text, or a list of texts in slot order
templateYesTemplate id, e.g. drake, db (Distracted Boyfriend), fine (This Is Fine)

Output Schema

NameRequiredDescriptionDefault
memesYes
creditNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: this is deterministic and non-AI, so the same inputs yield the same output, and it discloses that preview controls an inline image. No annotation contradiction: generating an image without mutating stored state is consistent with readOnlyHint=true.

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?

Three short sentences, front-loaded with the capability, then the prerequisite, then the input format and a worked example. No filler; every sentence carries operational information.

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, return values need no explanation, and the description covers prerequisite, both caption formats, and a valid example. Minor gap: the preview parameter's default and visual effect are left entirely to the schema.

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: it explains that the captions list is interpreted in slot order and that an object maps slot to text, then anchors that with a concrete 'drake' example. This resolves the anyOf ambiguity better than the schema alone.

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: putting the caller's exact words onto a classic template, with the qualifier 'Instant, no AI involved' that implicitly separates it from an AI-generation sibling like make_meme. It stops short of naming the alternative, so the contrast is inferential rather than explicit.

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?

'Use search_templates first to get the template id and its caption slots' gives a concrete prerequisite and ordering. What is missing is an explicit exclusion, e.g. when to prefer make_meme instead of this deterministic path.

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