Skip to main content
Glama
Sign In
MEME

MEME

by renniyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List rendered memes

list_memes

Lists rendered memes newest first, with optional filtering by user, so you can browse recent creations or a specific user's memes.

Instructions

Lists rendered memes (newest first), optionally filtered by user.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_memes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
userIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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. It usefully discloses sort order and optional filtering, but says nothing about default page size, whether results are paginated, or what a rendered meme record contains — gaps that matter for a list tool.

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?

A single well-formed sentence with the core behavior and sort order front-loaded and no wasted wording. Nothing could be trimmed without losing information.

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 two-optional-parameter read-only list tool with no output schema, the definition covers the essentials: what is listed, ordering, and the filter. The remaining omission (limit behavior) is modest given the tool's simplicity and lack of annotations.

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% and the description only partially compensates: "filtered by user" gives meaning to userId, but the limit parameter is never mentioned, so its default value and interaction with the schema's maximum of 100 must be guessed. Half the parameters remain unexplained beyond raw type constraints.

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 names a specific verb and resource ("Lists rendered memes") and adds the ordering ("newest first"), so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from siblings like get_meme or list_favorites, which is why 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 only implied: "optionally filtered by user" tells the agent the filter is optional, but there is no statement of when to reach for this versus get_meme (single item) or list_favorites. No prerequisites or exclusions are given.

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