Skip to main content
Glama
Sign In

memeboat-mcp

by at.memebo
OverviewDiscussionsAdmin

Server Details

Search 25,000+ meme templates and create shareable memes on memebo.at. Free, anonymous, no API key.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
13.6% over 78 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
memebo-at/memeboat-mcp
GitHub Stars
2
Server Listing
Memeboat MCP
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct step of the workflow: search the catalog, fetch one template by slug, and render a meme. The descriptions explicitly distinguish the slug-based lookup from the query-based search, leaving no realistic path to misselection.

Naming Consistency4/5

All three names follow a verb_noun pattern (search_meme_templates, get_meme_template, create_meme) in snake_case. The only deviation is the plural/qualifier in the template tools, which is still predictable and readable.

Tool Count4/5

Three tools is lean but each earns its place as a stage in the discover-inspect-create pipeline, with no redundancy. It sits at the thin end of the range but matches the narrow scope of a meme-generation service.

Completeness4/5

The core lifecycle — find a template, inspect its caption semantics, produce a shareable meme — is fully covered with no dead ends. Minor gaps exist (no listing or deleting of memes the user created, no template metadata update), but agents can work around them.

Available Tools

3 tools
create_memeCreate a memeAInspect

Create a real, shareable meme on memebo.at by captioning a template. texts are placed top-to-bottom: 1 caption = bottom text, 2 captions = classic top/bottom, N captions fill the template's boxes in order (match suggestedCaptionCount when possible). Returns the meme page URL and a direct image URL. Rate-limited per IP — space out repeated calls.

NameRequiredDescriptionDefault
fontNoDefault font for all captions, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew
styleNoAlternate background style name from get_meme_template's availableStyles, e.g. 'maga'
textsYesCaptions, top-to-bottom. Each is a string or { text, color?, outline?, font? } for per-caption styling. At least one must be non-empty.
layoutNolayout:'top' puts captions in a white bar above the image; 'default' overlays them on the image
templateYesTemplate slug, e.g. "x-x-everywhere"

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does reasonably well: it discloses the return artifacts (meme page URL plus direct image URL) and a per-IP rate limit with the mitigation of spacing calls. It does not say whether created memes are public/persistent or whether any auth or template availability constraints apply, which are the remaining behavioral gaps.

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?

Four sentences, each earning its place: purpose, caption-mapping rules, return values, rate limit. The core action is front-loaded in the first clause and nothing is padded or repeated from structured fields.

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?

For a create tool with no output schema, the description covers the essentials: what is produced, how the variable-length texts argument behaves, and the rate-limit constraint. It leaves out persistence/visibility and any prerequisite for obtaining a valid template slug, so it is strong but not exhaustive.

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%, so the schema already documents font, style, layout, template and per-caption styling, making 3 the baseline. The description does add genuine meaning the schema lacks — the positional semantics of texts (1 = bottom, 2 = top/bottom, N fills boxes in order) — which lifts it slightly, but the rest of the parameters are left entirely to the schema.

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?

The description opens with a specific verb and resource ('Create a real, shareable meme ... by captioning a template') and states the output artifacts (page URL and image URL). It doesn't explicitly name the sibling template tools to distinguish itself, but the create-vs-read split against get_meme_template and search_meme_templates is unambiguous from the verb alone.

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?

It gives concrete guidance on how many captions to supply and how they map to the template's boxes, and tells the agent to match suggestedCaptionCount where possible. It also warns about rate limiting and spacing out repeated calls. It stops short of explicitly saying 'use search_meme_templates first to find a slug,' which is the one missing routing instruction.

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

get_meme_templateGet meme template detailsAInspect

Fetch one meme template by its slug (from search_meme_templates or a memebo.at/templates/ URL): dimensions, image URL, suggested caption count and, when it has one, the meaning and origin of the meme with its sources.

NameRequiredDescriptionDefault
slugYesTemplate slug, e.g. "x-x-everywhere"

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses that meaning and origin are conditional ('when it has one') and that sources accompany them, which is real behavioral detail. It does not cover failure behavior for an unknown slug or any caching/auth traits, which keeps it from a 5.

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?

One sentence, front-loaded with the verb and resource, with the slug provenance in a tight parenthetical and the return contents following. Nothing is wasted and nothing essential is deferred.

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?

There is no output schema, and the description compensates by enumerating the returned fields, so an agent knows what it gets back. The only gap is behavior on a missing/invalid slug, which is minor for a single-parameter read.

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% and already includes an example slug format, yet the description still adds value by naming the two authoritative sources for a slug (search results, template URL). That provenance guidance is meaningfully beyond the schema.

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 ('Fetch one meme template by its slug') and enumerates exactly what comes back: dimensions, image URL, caption count, and optional meaning/origin. Referencing 'one' template plus slugs coming from search_meme_templates implicitly but clearly separates it from the sibling search tool.

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?

Tells the agent precisely how to obtain the required input: from search_meme_templates or a memebo.at/templates/<slug> URL, which is the key routing decision against the sibling. It stops short of explicit exclusions (e.g., 'do not use this to list templates'), so a 4 rather than a 5.

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

search_meme_templatesSearch meme templatesAInspect

Search memebo.at's catalog of 25,000+ meme templates by name, other names or topic (e.g. "drake", "distracted boyfriend", "cat"). Returns matching templates with their slug (use it with create_meme), image URL and a suggested caption count.

NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesSearch terms, e.g. "surprised pikachu"

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does well to disclose what comes back (slug, image URL, suggested caption count) and the catalog scale, but it never states ranking behavior, what happens on zero matches, or that the operation is a safe read — gaps that matter more without annotations.

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, zero waste. The search scope and examples come first, and the downstream handoff to create_meme follows, so the information is front-loaded exactly where an agent needs it.

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 only two parameters and no output schema, the description covers the essentials: search dimensions, return fields, and the cross-tool linkage. It stops short of the search-behavior details (fuzzy matching, ordering, empty-result handling) that an agent might want, but nothing critical is missing.

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; the description earns more by explaining that the query field accepts names, alternate names, or topics and giving example queries ("drake", "distracted boyfriend", "cat"). The limit parameter is left to the schema, but it is fully documented there.

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?

The description states a specific verb (search) and a specific resource (memebo.at's catalog of 25,000+ meme templates), and narrows the search dimensions to name, alternate names, or topic with concrete examples. It also distinguishes itself from create_meme by noting that the returned slug is the input for that tool, so an agent can place it in the workflow without opening any 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?

The description makes clear when this tool applies (you need to find a template) and hands off downstream by saying "use it with create_meme." It does not mention the get_meme_template sibling or say when to prefer it over this search, which is the only routing gap.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Changedcreate_meme5 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • removedInput schema / additionalProperties
        Removed value: -false
      • removedInput schema / properties / font / $ref
        Removed value: -"#/properties/texts/items/anyOf/1/properties/font"
      • addedInput schema / properties / font / type
        Added value: +"string"
      • changedInput schema / properties / texts / items / anyOf
        Previous value: -[
-  {
-    "maxLength": 200,
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "color": {
-        "description": "Caption fill color: hex or white/black/red/yellow/blue/green",
-        "type": "string"
-      },
-      "font": {
-        "description": "Caption font, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
-        "type": "string"
-      },
-      "outline": {
-        "description": "Caption outline color; omit for an auto-picked readable outline",
-        "type": "string"
-      },
-      "text": {
-        "maxLength": 200,
-        "type": "string"
-      }
-    },
-    "required": [
-      "text"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "maxLength": 200,
+    "type": "string"
+  },
+  {
+    "properties": {
+      "color": {
+        "description": "Caption fill color: hex or white/black/red/yellow/blue/green",
+        "type": "string"
+      },
+      "font": {
+        "description": "Caption font, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
+        "type": "string"
+      },
+      "outline": {
+        "description": "Caption outline color; omit for an auto-picked readable outline",
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 200,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  }
+]
    • Changedget_meme_template2 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedsearch_meme_templates2 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 1 tool update
    • Changedcreate_meme7 fields changed
      • addedInput schema / properties / font
        Added value: +{
+  "$ref": "#/properties/texts/items/anyOf/1/properties/font",
+  "description": "Default font for all captions, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew"
+}
      • addedInput schema / properties / layout
        Added value: +{
+  "description": "layout:'top' puts captions in a white bar above the image; 'default' overlays them on the image",
+  "enum": [
+    "default",
+    "top"
+  ],
+  "type": "string"
+}
      • addedInput schema / properties / style
        Added value: +{
+  "description": "Alternate background style name from get_meme_template's availableStyles, e.g. 'maga'",
+  "maxLength": 60,
+  "minLength": 1,
+  "type": "string"
+}
      • changedInput schema / properties / texts / description
        Previous value: -"Caption strings, top-to-bottom. At least one must be non-empty."New value: +"Captions, top-to-bottom. Each is a string or { text, color?, outline?, font? } for per-caption styling. At least one must be non-empty."
      • addedInput schema / properties / texts / items / anyOf
        Added value: +[
+  {
+    "maxLength": 200,
+    "type": "string"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "color": {
+        "description": "Caption fill color: hex or white/black/red/yellow/blue/green",
+        "type": "string"
+      },
+      "font": {
+        "description": "Caption font, one of: impact, arial, helvetica, times, courier, titillium, thick, kalam, comic, notosans, notosanshebrew",
+        "type": "string"
+      },
+      "outline": {
+        "description": "Caption outline color; omit for an auto-picked readable outline",
+        "type": "string"
+      },
+      "text": {
+        "maxLength": 200,
+        "type": "string"
+      }
+    },
+    "required": [
+      "text"
+    ],
+    "type": "object"
+  }
+]
      • removedInput schema / properties / texts / items / maxLength
        Removed value: -200
      • removedInput schema / properties / texts / items / type
        Removed value: -"string"
  3. 3 tool updates
    • First observedcreate_meme
    • First observedget_meme_template
    • First observedsearch_meme_templates

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources