Skip to main content
Glama

sok_vinster

Read-only

Namnsökningen avser sidor om spel, spelstudior och samlingar. Endast sidnamn som innehåller angiven text matchas; ämne, tema och beskrivning används inte. Publicerade speltester: 29

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": {
      "s": "<s>"
    },
    "name": "sok_vinster"
  }
}

Input Schema

NameRequiredDescriptionDefault
sYesFältet accepterar namnet eller en del av namnet på ett spel, en spelstudio eller en samling, med minst två tecken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/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 useful behavioral detail beyond annotations: matching is limited to page names and does not use subject, theme, or description. The final sentence about published game tests is ambiguous but does not contradict 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.

Conciseness3/5

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

The first two sentences are front-loaded and efficient, stating the search scope and matching rule. The final sentence, 'Publicerade speltester: 29', is a dangling statistic whose relevance to invoking the tool is unclear. It slightly weakens an otherwise compact definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only search tool with no output schema, the definition covers the essential scope, matching semantics, and a negative constraint about fields not searched. It does not describe result ordering, pagination, or return shape, but those gaps are modest given the tool's simplicity and the presence of annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameter is already well documented as accepting a game, studio, or collection name or partial name of at least two characters. The description adds meaning beyond the schema by clarifying that matching is strictly against page names rather than content fields. This helps the agent understand how the string parameter is interpreted.

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 specific search behavior: it searches page names for pages about games, game studios, and collections. It also clarifies that only page names containing the given text are matched, which makes the tool's scope clear. It does not explicitly distinguish itself from the sibling tools gratis_vinster and vinster.

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 through the scope statement that the search covers games, studios, and collections, and through the exclusion of subject, theme, and description fields. This tells the agent what the tool is for, but there is no explicit guidance on when to use it instead of the sibling tools. No alternatives are named.

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