Skip to main content
Glama

spelautomater_sok

Read-only

Sidor matchas på namn som innehåller angiven text, för spel, spelstudior och samlingar. Ämne, tema och beskrivning ger inga träffar. Spelrecensioner: 22

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

Input Schema

NameRequiredDescriptionDefault
sYesSökvärdet består av ett fullständigt namn eller en del av namnet till ett spel, en spelstudio eller en samling och har minst två tecken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare a read-only, closed-world lookup, so the safety profile is covered. The description adds genuine behavioral context beyond that: matching is substring-based on names only, and theme/subject/description fields are not searchable. It omits result ordering, limits, pagination and case sensitivity, and the "Spelrecensioner: 22" fragment adds no interpretable behavior.

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 matching rule and the negative scope are front-loaded and earn their place, but the dangling "Spelrecensioner: 22" line is cryptic noise that a reader cannot act on. Three short sentences, one of which is wasted.

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 search with no output schema and read-only annotations, the description covers the essential matching semantics and the excluded fields. It leaves out what the response contains and how many results are returned, and the unexplained trailing fragment lowers confidence that the description is complete.

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 parameter already documents the two-character minimum and max length. The description restates that the value is a full or partial name of a game, studio or collection, adding modest scope clarification but no format or example beyond the schema.

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 matching operation: pages are matched on names containing the given text, scoped to games, game studios and collections. That is enough specificity for an agent to know this is a name-substring search rather than a curated list like the siblings. The trailing fragment "Spelrecensioner: 22" is opaque and slightly muddies the purpose, and no sibling is named.

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?

It gives explicit negative guidance that subject, theme and description produce no matches, which tells the agent when NOT to reach for this tool. There is no positive when-to-use framing or explicit comparison to alternatives such as the sibling list tools, so the routing guidance is implied rather than stated.

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