Skip to main content
Glama

basta_spelautomater

Read-only

Återger det som visas på en webbsida, närmare bestämt fakta om ett spel eller en spelförteckning, när sidans adress anges.

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

Input Schema

NameRequiredDescriptionDefault
urlYesBåda varianterna godtas för en sida på webbplatsen: hela adressen eller delen som inleds med snedstreck.

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?

The annotations already declare this a read-only, non-open-world operation, so the safety profile is covered. The description adds the scope that the returned content is game or listing facts rather than general page text, which is useful. It says nothing about how the page is fetched, whether failures are common, or rate limits, so it does not go beyond 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.

Conciseness4/5

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

A single front-loaded sentence that identifies the action and the scope, with no filler beyond the slightly padded 'närmare bestämt'. It is well within an appropriate length for a one-parameter tool.

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 one documented required parameter, no output schema, and read-only annotations, the definition is minimally adequate. It leaves unclear what shape the 'spelförteckning' result takes and how this differs from the search sibling, which an agent would need in order to choose correctly.

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 description coverage is 100%, and the schema already explains that either a full URL or a slash-prefixed path to a page on the site is accepted. The description only restates that a page address is supplied, adding no format or example detail. Baseline 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 gives a specific verb and resource: it retrieves page content, narrowed to facts about a game or a game listing ('fakta om ett spel eller en spelförteckning'). That is more precise than the name 'basta_spelautomater' alone. It never distinguishes this from the sibling spelautomater_sok, so an agent cannot tell the two apart from this text.

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 only implied: call it when you have the address of a page ('när sidans adress anges'). There is no statement of when to prefer this over spelautomater_sok or gratis_vinster, and no exclusions or prerequisites.

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