Skip to main content
Glama
Sign In
memgrep

memgrep

by Milflopper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_memes

Find memes with natural language queries. Search a meme collection semantically in Russian or English to retrieve matching images, captions, and file paths.

Instructions

Semantic search over the meme collection. Query in Russian or English.

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": {
      "query": "<query>"
    },
    "name": "search_memes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden; it does convey that matching is semantic rather than exact and that the query language is flexible. It does not state read-only behavior, result ordering, or limitations, but for a simple search tool the disclosed traits are non-trivial.

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 short sentences carry the essential message, with the main action stated first and no filler. Every phrase earns its place.

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 two-parameter search with an output schema, the description is nearly sufficient, but it leaves two gaps: the meaning/behavior of 'k' and the relationship to the sibling get_meme tool. This is adequate but not complete.

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 0%, so the description must compensate. It adds meaning to 'query' by explaining the search is semantic and accepts Russian or English, but it remains silent on the 'k' parameter. The compensation is partial, making this minimum viable.

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 gives a specific verb and resource ('Semantic search over the meme collection') and the 'semantic' qualifier distinguishes it from a direct fetch like get_meme. It is clear, but it does not explicitly name or contrast the sibling tool.

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?

The phrase 'Semantic search over the meme collection' implies when the tool is relevant, and 'Query in Russian or English' gives practical input guidance. However, it offers no explicit direction on when to choose this over get_meme or what types of queries are not appropriate.

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