Skip to main content
Glama
Sign In
MEME

MEME

by renniyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export a meme

export_meme

Exports a meme as SVG or PNG plus a sidecar JSON with concept, sources, attribution, license, and disclaimer data, enabling compliant sharing and provenance tracking.

Instructions

Exports a meme as SVG or PNG plus a sidecar JSON (concept, sources, attribution, license, disclaimer).

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

Input Schema

NameRequiredDescriptionDefault
formatNopng
memeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/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. It does disclose the deliverable shape well (image plus a sidecar JSON containing concept, sources, attribution, license, disclaimer), which is real value. It says nothing about whether output is written to disk, returned as a URL/base64, or what permissions or side effects are involved.

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?

A single tight sentence with the resource and output artifacts front-loaded. Nothing is wasted, though the parenthetical list is dense and could be unpacked for readability.

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

Completeness3/5

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

With no output schema and no annotations, the description does cover what the export produces, which is the biggest gap it could have filled. It still leaves the agent unsure about the transport of the result (file, URL, inline data) and about the required memeId's meaning.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for both parameters. It restates the format enum values (SVG/PNG) already visible in the schema and adds no detail about defaults or tradeoffs, and it never mentions memeId at all.

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 (exports) and resource (a meme), plus the concrete output formats (SVG or PNG) and the sidecar JSON. It does not distinguish itself from the nearby render_meme or get_meme siblings, so an agent must infer the boundary.

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 when-to-use or when-not-to-use guidance. With siblings like render_meme and get_meme present, the description gives no signal about which one an agent should pick for a given request.

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

Deploy Server

Other Tools