MEME

Overview Schema Source Related Servers Discussions Admin

Get a meme

get_meme

Retrieve a complete meme record by ID—including concept, text, quality, sources, and attribution—to inspect or reuse meme details.

Instructions

Full meme record: concept, texts, quality, sources, attribution.

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": {
      "memeId": "<memeId>"
    },
    "name": "get_meme"
  }
}

Input Schema

Name	Required	Description	Default
`memeId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

C2.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about read-only semantics, permissions, or failure modes. Its only real disclosure is which fields come back (concept, texts, quality, sources, attribution), which is mild value but falls short for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no waste, and the most useful information (the returned record's contents) is front-loaded. However, the telegraphic colon-list style leaves it under-specified rather than genuinely well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter lookup this could be adequate, and there is no output schema to explain returns, so listing return fields helps. But with no annotations, no parameter documentation, and no return-format or failure detail, an agent lacks what it needs to call it confidently.

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

Parameters1/5

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

The single parameter memeId has 0% schema description coverage, and the description never explains what a meme ID is, where to obtain one, or its format. With one undocumented required parameter, the description does nothing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase field list ("Full meme record: concept, texts, quality, sources, attribution") rather than a verb+resource statement; the retrieval action is only inferable from the name and title "Get a meme". It hints at the difference from list_memes by promising a "full record," but never explicitly contrasts with siblings like list_memes or render_meme.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus list_memes (to enumerate) or render_meme (to get an image). No prerequisites, ID source, or error condition (e.g., unknown memeId) is mentioned, so the agent must infer usage entirely from the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.