Skip to main content
Glama

hry_vysledky

Read-only

Funkce vrací stránky her, herních studií a kolekcí, jejichž název obsahuje zadaný text. Shoda s tématem, námětem nebo popisem se nezjišťuje. Herní recenze: 31

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

Input Schema

NameRequiredDescriptionDefault
qYesČást názvu hry nebo studia o délce alespoň dvou znaků stačí k vyhledání.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered structurally. The description adds real behavioral value by disclosing the name-only matching rule (topic/theme/description are ignored), which affects result expectations. It does not disclose result ordering, paging limits, or what "stránky" (pages) means, and the trailing "Herní recenze: 31" conveys nothing actionable.

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 two opening sentences are front-loaded and waste no words. The final fragment "Herní recenze: 31" is unexplained noise that appears to be a leftover annotation and slightly undermines the otherwise tight structure.

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 one-parameter read-only search this is mostly adequate: the matching rule and ignored fields are stated, and annotations cover the safety profile. Since there is no output schema, the description should at least sketch what a result entry or page looks like (paging, limits, mixed entity types), which it does not.

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 100% and the single parameter q already documents the minimum two-character prefix/substring rule. The description reinforces that only the name field is searched, which slightly sharpens q's meaning, but adds no format, encoding, or edge-case guidance beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 first sentence states a specific verb and resource set: it returns pages of games, game studios and collections whose name contains the supplied text. The second sentence usefully narrows scope by ruling out topic/theme/description matching, though the unrelated trailing fragment "Herní recenze: 31" muddies the purpose and does not map to any behavior.

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 agent can infer this is a name-substring lookup and that it is not a full-text/thematic search, which is genuinely helpful. However, no sibling tool is named (online_hry, online_vyhry) and there is no explicit statement of when to pick this tool over another, nor any note about pagination or result caps.

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