Skip to main content
Glama

darmowe_automaty

Read-only

Pobiera treść strony wskazanej adresem i oddaje zawarte na niej informacje o grze bądź 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": "darmowe_automaty"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWartością pola jest pełny adres strony tej witryny lub jej część od ukośnika.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, and the schema note that the URL must belong to 'this site' is consistent with the closed-world hint, so there is no contradiction. The description adds the useful behavioral detail that the response is either game details or a game listing, but it says nothing about failure behavior for invalid or off-site URLs or about the response shape.

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?

A single sentence with no filler, leading with the fetch action and following with the returned content. Nothing is padded, though the sentence packs two possible return types into one clause a bit loosely.

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 fetch tool with no output schema, the description covers the action and the general nature of the result, which is close to sufficient. It falls short on how the two possible result kinds are distinguished and on what happens when the URL is invalid or points outside the site.

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% for the single url parameter, and the schema description already explains the accepted full-URL-or-path-suffix form. The description's phrase 'strony wskazanej adresem' merely restates the parameter's role without adding format, encoding, or validation meaning, so the baseline of 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 states a concrete verb and resource: it fetches the page at the given URL and returns either game information or a game list found on it. That is more specific than the tool name 'darmowe_automaty' alone, but it does not distinguish itself from the sibling szukaj_gry, which plausibly serves a similar 'find games' intent.

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 when-to-use guidance, no statement of when to prefer this over szukaj_gry or jackpoty_online, and no prerequisites or exclusions. The only implicit cue is that the caller must already have a page address, which the schema already makes obvious via the required url field.

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