Skip to main content
Glama

vinster

Read-only

Hämtar sidinnehållet för en webbadress: antingen fakta om ett spel eller listan över flera 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": "vinster"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSidadress i sin helhet eller med inledande 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, so the safety profile is covered; the description adds the useful detail that the response is either single-game facts or a multi-game list, which partially compensates for the absent output schema. It says nothing about error behavior, rate limits, or what happens with malformed URLs.

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 with the action front-loaded and the two outcome types appended. No filler, though the colon-split construction makes it slightly dense for a single line.

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 tool with full schema coverage and annotations, the definition is minimally sufficient, and the hint about the two return shapes helps since there is no output schema. It is still thin on how to pick between this and the sibling search/list tools.

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% and the single url parameter is already documented as a full address or a path with a leading slash. The description adds no extra meaning about accepted URL forms or site restrictions, so the 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?

States a concrete verb and resource in Swedish: "Hämtar sidinnehållet för en webbadress" (fetches the page content of a URL), and even names the two possible return shapes (game facts vs. list of games). This is clearly more specific than the bare name "vinster", though it never distinguishes itself from siblings gratis_vinster or sok_vinster.

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 or when-not-to-use guidance at all, and no mention of the sibling tools that likely cover the same prize domain. The agent must infer that this is the 'fetch by URL' entry point purely from the parameter shape.

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