Skip to main content
Glama

Memeoki

Find meme templates

search_templates
Read-onlyIdempotent

Search 1800+ classic meme templates by name, nickname or idea ("drake", "distracted", "choice", "panic"). Returns each template's id, caption slots (with what goes in each), what the meme means, example captions and a blank image. Use before caption_template.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoA name, nickname or idea. Leave empty for the most popular templates.

Output Schema

NameRequiredDescriptionDefault
templatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds value beyond that by disclosing the corpus size and the shape of each result (id, caption slots with fill instructions, meaning, example captions, blank image), which tells the agent what it gets back before calling.

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?

Two sentences, front-loaded with the search capability and example queries, then a compact workflow hint. No filler or restatement of the tool name.

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 rich annotations, an output schema and a simple two-parameter surface, the definition covers nearly everything an agent needs to invoke it correctly. The only omission is guidance on the limit parameter and result-set size, a minor gap for such a low-complexity tool.

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 50%: the query parameter is documented in the schema, and the description reinforces it with example values that reveal nickname/idea matching rather than exact-name matching. The limit parameter is undocumented in both places (default 10, max 25), so the description only partially compensates for the coverage gap.

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?

States a specific verb and resource ("Search 1800+ classic meme templates") plus the three matching axes (name, nickname, idea) with concrete example queries. An agent can distinguish this from caption_template and make_meme without opening either schema.

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 before caption_template" gives an explicit sequencing rule that routes the agent into the correct workflow. It stops short of stating when not to use it (e.g. when you already have a template id), so it is clear context rather than a full when/when-not rule set.

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