Skip to main content
Glama

jackpoty_szukaj

Read-only

Wyszukuje strony, których nazwa zawiera podany tekst: strony gier, studiów gier i kolekcji. Nie obejmuje tematu, motywu ani opisu. Nasze recenzje gier: 32

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": {
      "fraza": "<fraza>"
    },
    "name": "jackpoty_szukaj"
  }
}

Input Schema

NameRequiredDescriptionDefault
frazaYesPole przyjmuje pełną nazwę gry, studia albo kolekcji bądź dowolny fragment takiej nazwy, co najmniej dwa znaki.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 the safety profile is covered. Beyond that the description only clarifies that matching is against page names, with no mention of result ordering, caps, or pagination — modest added value against the annotation baseline.

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 first two sentences are tightly front-loaded and earn their place. The trailing fragment 'Nasze recenzje gier: 32' is an unrelated dangling artifact that adds noise without describing behavior.

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 no output schema, the description covers what is matched, which entity types are included, and what is excluded. Only the shape of results (ordering, limits) is left implicit, which is a minor gap at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the two-character minimum and fragment/whole-name acceptance are already documented. The description nevertheless adds real matching semantics — that the term is compared against the page name only, not theme or description — which the schema does not state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — searches pages whose name contains the given text — and enumerates the entity types covered (games, studios, collections). The explicit exclusion of topic/theme/description makes the scope unambiguous and separates it from any content-based search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear usage context is given: use it for name-based lookup across three page types, and it deliberately does not search themes or descriptions. What is missing is routing to an alternative for those excluded cases, so the agent knows the boundary but not where to go next.

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