Skip to main content
Glama

basta_jackpottar

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

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

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, so safety and scope are covered elsewhere. The description adds that the response contains game details or a game list, which is modest but real context about the return content. It says nothing about rate limits, error behavior when the page is not a game page, or response format.

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 clauses, front-loaded with the input and then the output; nothing is padded. The only weakness is that the alternative outputs ('a game' vs 'the list of games') are run together without saying how the caller can tell them apart.

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 with no output schema, the description covers the minimum: input is a URL, output is page content about a game or games. It leaves open the output shape and what happens on non-game pages, which matters because the return value is untyped.

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%, so the single url parameter, including its maxLength and full-or-relative-path rule, is already documented in the schema. The description restates the same idea without adding format, canonicalization, or failure semantics. Baseline 3 applies.

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 states a concrete action (takes a URL, returns the page's contents) and a rough resource (a game's details or the list of games). However, it reads as a generic page-fetch and gives no hint as to how it relates to its own name ('basta_jackpottar') or to siblings like topp_jackpottar. An agent knows it fetches, but not clearly what makes this the 'best jackpots' tool.

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 guidance on when to choose this tool over topp_jackpottar or hitta_vinster, nor on which URLs are appropriate to pass. The only implied usage is 'give it a page address', which the schema already says.

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