Skip to main content
Glama
Sign In
MEME

MEME

by renniyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Report a meme

report_content

Report a meme for moderation review by specifying its ID and a reason such as offensive, inaccurate, copyright, spam, or other; hostile details are redacted.

Instructions

Report a meme for review. Reasons: offensive, inaccurate, copyright, spam, other. Reports are always filed; hostile details are redacted by moderation.

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>",
      "reason": "<reason>"
    },
    "name": "report_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
memeIdYes
reasonYes
detailsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose two useful traits: reports are always filed, and hostile details are redacted by moderation. It still leaves gaps – whether duplicate reports are accepted, whether the report is idempotent, and what the caller gets back.

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?

Three short sentences, front-loaded with purpose and followed by enum values and behavioral notes. Nothing is padded or redundant.

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?

For a simple 3-parameter mutation with no output schema and no annotations, the description covers purpose and moderation behavior but omits the outcome of a report (success signal, queue placement) and the semantics of the details parameter. Adequate but not complete.

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 enumerates the reason values (already present in the schema enum, so no net gain) but says nothing about memeId constraints or the optional details field, including that details is a free-text note capped at 1000 characters and may be redacted.

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 and resource ('Report a meme for review'), which is clearly distinct from sibling operations like rate_meme, edit_meme or review_moderation_queue. It does not explicitly name a sibling or contrast with one, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by 'for review' – the caller should use it when content needs moderator attention. There is no explicit when-not guidance, no mention of prerequisites (e.g. must the meme exist), and no pointer to review_moderation_queue for follow-up.

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