Skip to main content
Glama
Sign In
MEME

MEME

by renniyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Favorite a meme

favorite_meme

Saves a meme as a favorite and lets you set or update a short note for later reference.

Instructions

Adds (or updates the note on) a favorite.

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

Input Schema

NameRequiredDescriptionDefault
noteNo
memeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/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 burden. It does disclose useful upsert semantics — that an existing favorite's note can be replaced — but says nothing about idempotency, what happens if the memeId does not exist, required permissions, or what the call returns.

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 sentence with no padding, and the upsert detail is correctly packed into the parenthetical. However, brevity here reads as under-specification rather than efficiency, since core facts (the meme resource, the parameters) are omitted.

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 mutation tool with no annotations, no output schema, and 0% parameter documentation, the description is far too thin. An agent would need to guess the semantics of favoriting an already-favorited meme and the meaning of both arguments.

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. It only hints at the optional note field via "updates the note"; memeId, its required status, and the 300-character note limit are never mentioned, leaving the agent to read types and constraints out of raw JSON Schema.

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?

"Adds (or updates the note on) a favorite" gives a verb and a resource, but the resource is described abstractly as "a favorite" rather than stating that it marks a specific meme as favorited. The meme identity only surfaces via the parameter name, and nothing distinguishes this from siblings like list_favorites or delete_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 guidance on when to call this versus alternatives such as list_favorites (to check existing favorites) or delete_meme (to remove one). No preconditions or exclusions are stated, leaving the agent to infer that this is the write path for favoriting.

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