Skip to main content
Glama

spiele

Read-only

Ermittelt anhand einer Adresse, welche Informationen eine Seite dieser Website enthält: Details zum Spiel oder die Auflistung der Spiele.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAkzeptiert werden entweder die vollständige Seitenadresse oder der mit Schrägstrich beginnende Rest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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, and the description is consistent with both by scoping the tool to 'dieser Website'. It adds genuine behavioral value by disclosing that the response is polymorphic (either single-game details or a game listing), but says nothing about invalid addresses, missing pages, or 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?

One compact sentence, front-loaded with the input basis and immediately followed by the two possible outcomes. No filler, though the phrasing 'welche Informationen eine Seite enthält' is slightly roundabout compared with simply stating what is returned.

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 simple read-only, single-parameter tool this covers the essentials, and it usefully sketches the two return cases in the absence of an output schema. It still leaves open what happens on a non-game page or an invalid URL, which matters because openWorldHint=false makes address validity the agent's responsibility.

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 coverage, the schema already explains that a full page URL or a slash-prefixed remainder is accepted. The description only repeats 'anhand einer Adresse' and adds no format, example, or validity constraints beyond the structured field.

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 gives a specific verb ('Ermittelt') plus an explicit resource and result set ('Details zum Spiel oder die Auflistung der Spiele'), so an agent knows this is a URL-keyed page-content lookup for games. It is not tautological like the bare name 'spiele', but it never explicitly contrasts itself with the sibling 'suchen_slots', so the differentiation is only implicit.

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 rather than stated: 'anhand einer Adresse' tells the agent it must already have a page address, and the two possible outcomes hint at what the caller can expect. There is no explicit when-to-use/when-not guidance and no routing to the search sibling for cases where the agent lacks a URL.

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