webhallen-mcp

List Webhallen stores

list_stores

List physical Webhallen stores with id, name, city, and address. Use each store id with the inStock filter to check local stock availability.

Instructions

All physical Webhallen stores with id, name, city and address. Use the id with the inStock filter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stores"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden, and it does disclose the operation's nature: a read-only enumeration of physical stores with a known field set. The zero-parameter, zero-risk shape means little else needs disclosing, though it doesn't mention result ordering or whether the list is exhaustive/static.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two short sentences, front-loaded with the resource and returned fields, followed by one actionable note. Every clause earns its place and nothing is padded.

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?

Given no output schema, the description correctly compensates by naming the returned fields, and the tool's complexity is minimal. The only small gap is the absence of any hint about result size, ordering, or whether the store list is stable, which would help an agent decide when to re-call.

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?

The tool takes zero parameters, so there are no semantics to clarify; the baseline for a parameterless tool applies. The description's mention of the returned id is useful downstream context but does not substitute for parameter documentation, which isn't needed here.

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 opens with a specific verb and resource ('All physical Webhallen stores') and enumerates the returned fields (id, name, city, address), so an agent immediately knows this is a static store listing. It doesn't contrast itself with siblings like search_products or get_product, but none of those cover stores, so differentiation is implicit rather than stated.

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?

The second sentence gives downstream guidance ('Use the id with the inStock filter'), which tells the agent why to call this tool. However, there is no explicit statement of when to use it versus the sibling tools and no exclusions or prerequisites; the usage context is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server