Skip to main content
Glama

GIF-keresés

search_gifs
Read-onlyIdempotent

Ingyenes GIF-ek keresése a Kódvéna GIF-tárában (robot reakció-GIF-ek), letöltési és beágyazási linkkel.

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": {
      "q": "<q>"
    },
    "name": "search_gifs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesKeresőszó, pl. köszönöm, gratulálok, péntek

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results carry download and embed links, which is genuinely useful since there is no output schema, but it says nothing about result counts, pagination, or query language handling.

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 action and resource, with the scope qualifier and the return-link detail packed into it. Nothing is redundant or padded.

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 one-parameter read-only search with full annotation coverage, the description supplies scope, content type, and return payload. Only minor gaps remain, such as result limits and whether queries must be in a particular language.

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?

With a single parameter and 100% schema description coverage (including example terms like 'köszönöm', 'gratulálok', 'péntek'), the schema already does the work. The description adds no further meaning about the query parameter, so the baseline 3 applies.

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 ('GIF-ek keresése') and narrows scope to the provider's own library with a stated content type ('robot reakció-GIF-ek'), which effectively separates it from generic web search siblings. It does not name a sibling it is not, so it stops short of the top score.

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: the parenthetical 'robot reaction GIFs' hints at the intended scenario, and the library scoping implies this is not a general image search. There is no explicit when-to-use, when-not-to-use, or alternative-tool routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources