Skip to main content
Glama

Slots Utan Licens SE

basta_slots

Read-only

Tar emot en webbadress till en sida. Returnerar sidans innehåll med uppgifter om ett spel eller listan över spel.

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_slots"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWebbadressen till en sida på webbplatsen, fullständig eller inledd med snedstreck.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that the response contains either a single game's details or a list of games, which hints at variable return shape. It says nothing about invalid URLs, missing pages, or how the two response shapes are distinguished, so it adds only moderate value beyond the annotations.

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?

Two short sentences, front-loaded with the input and then the output, with no obvious padding. The brevity comes at a small cost in precision ('sidans innehåll' is vague), but there is no wasted wording.

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 with full schema coverage, the description covers input and output shape adequately for calling it. However, it omits how this tool relates to its two siblings and what happens on an invalid or empty URL, both of which an agent needs to select and use it confidently.

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?

There is a single parameter at 100% schema description coverage; the schema already explains that the value is a full web address or a path beginning with a slash. The description only restates that a web address is received and adds no format, host, or encoding detail. Baseline 3 is appropriate when the schema does the work.

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 pair: it takes a web address and returns the page's content, specifically game details or a list of games. That is clear enough to understand the operation. It does not differentiate against the sibling tools gratis_vinster and sokning_vinster, nor does it explain what 'slots' means here, so it stops short of a 5.

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 use this versus the sibling tools, no prerequisites, and no exclusions. The only guidance is implicit in 'a page about a game or the list of games', leaving the agent to infer that this is a fetch-by-URL operation rather than a search.

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