Skip to main content
Glama

hledat_vyhry

Read-only

Tento nástroj vybírá stránky her, herních studií a kolekcí podle toho, zda jejich název obsahuje zadaný text. Téma, námět ani popis nejsou vyhledávacím kritériem. Počet herních recenzí: 19

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

Input Schema

NameRequiredDescriptionDefault
qYesPole přijímá celý název nebo jeho část o délce alespoň dvou znaků.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real behavior by defining the match semantics (substring of the name) and the entity types covered (games, studios, collections). It omits pagination and result formatting, and the trailing sentence about the number of game reviews is unexplained noise rather than disclosure.

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?

The purpose is front-loaded in the first sentence and the exclusion rule follows logically. The final sentence ('Počet herních recenzí: 19') is dangling, unconnected context that does not help an agent decide or invoke, weakening an otherwise tight description.

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 single-parameter read-only lookup with full schema coverage and no output schema, the description covers what is searched, what is matched, and what is not matched. The only real gaps are return-shape/pagination expectations and the ambiguous trailing statistic, which are minor at this complexity.

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 description coverage is 100% and the single parameter q already documents that it accepts a full or partial name of at least two characters. The description adds the framing that matching is against the entity name, but no syntax, case-sensitivity, or accent-handling details beyond the schema, 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?

The description names a specific verb and resource set: it selects pages of games, game studios, and collections based on whether their name contains the given text. It also narrows the matching rule (name only, not theme/subject/description), which lets an agent distinguish it from a full-text search. It does not contrast itself with the sibling tools, so it stops 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?

There is useful negative guidance: theme, subject, and description are explicitly not search criteria, which steers an agent away from using this for topical lookups. However, no positive when-to-use framing or reference to alternatives (e.g., browsing free games or slots) is given, so the routing guidance is only implied.

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