Skip to main content
Glama

nowe_wygrane

Read-only

Zawartość pojedynczej strony witryny, wskazywanej adresem: opis gry albo spis gier.

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": {
      "url": "<url>"
    },
    "name": "nowe_wygrane"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPole przyjmuje pełny adres strony tej witryny albo samą ścieżkę od ukośnika.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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; the description corroborates the closed-world scope with 'tej witryny' and adds that the returned page is either a game description or a game listing. It still says nothing about response format, size, or what happens for an invalid path.

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?

One lean sentence that front-loads the resource and then qualifies the content type. No filler, though the terseness leaves the name mismatch unexplained.

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?

With no output schema, the description must carry the return-value burden, and it only vaguely says the page contains a game description or a game list. For a one-parameter fetch tool this is minimally adequate, but the name/behaviour gap and absent output detail keep it at a 3.

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 at 100% schema description coverage, the schema already explains that a full URL or a slash-prefixed path is accepted. The description repeats the address-based addressing model but adds no format, encoding, or validation detail beyond it.

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

Purpose3/5

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

The description names the resource precisely ('Zawartość pojedynczej strony witryny') and hints at the payload ('opis gry albo spis gier'), but it is a noun phrase with no explicit verb and never reconciles the tool name 'nowe_wygrane' (new wins) with the stated behaviour of fetching arbitrary page content, leaving real ambiguity about what the agent will receive.

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

Usage Guidelines2/5

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

There is no statement of when to pick this tool over the siblings 'sloty_szukaj' or 'top_jackpoty', no prerequisites, and no exclusions. The agent must infer that this is the generic page-fetch fallback from the schema alone.

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