Skip to main content
Glama

szukaj_gry

Read-only

Narzędzie zwraca strony gier, studia gier i kolekcje, których nazwa zawiera podany ciąg znaków. Temat, motyw i opis nie są przeszukiwane. Recenzje i testy gier: 20

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": {
      "s": "<s>"
    },
    "name": "szukaj_gry"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesPole służy do wpisania pełnej nazwy gry, studia lub kolekcji bądź tylko jej części, przy czym wpis liczy co najmniej dwa znaki.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 is covered and the description's added value is the disclosure that matching is strictly name-substring against a closed index. That is genuinely useful behavior context. However, the cryptic 'Recenzje i testy gier: 20' line is unexplained, leaving an agent unsure whether there is a hard result cap or an excluded content type.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is front-loaded with the resource and matching rule, and the negative-scope sentence immediately follows, so the useful content comes first with no filler. The closing fragment 'Recenzje i testy gier: 20' is dangling and does not clearly earn its place, which keeps this from a 5.

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 search with a fully described schema and annotations covering the safety profile, the description supplies enough to call it correctly. The only gap is the ambiguous trailing fragment, which leaves a small question about result limits or excluded content types; no output schema exists, so return-value detail is not required.

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 schema already documents the 2-64 character range and the partial-name semantics. The description restates the substring-matching idea ('nazwa zawiera podany ciąg znaków') but adds no formatting, encoding or normalization rules beyond the schema. Baseline 3 applies when the schema carries the parameter meaning.

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 uses a specific verb-plus-resource statement: it returns game, studio and collection pages whose name contains the given string, and it explicitly narrows scope by saying topic, theme and description are not searched. That negative scoping is what lets an agent predict which queries will succeed. It does not name or contrast sibling tools such as darmowe_automaty or jackpoty_online, so 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 implied by the negative constraint: an agent learns to search by name only, never by topic, theme or description, which is real guidance about when this tool fits. There is no explicit statement of when to use this versus an alternative tool, and the trailing 'Recenzje i testy gier: 20' fragment does not clarify whether it is a routing hint, a scope exclusion or a result limit.

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