Skip to main content
Glama

search

Search Ski Club of Great Britain website content (articles, holidays, ski tests, discounts, resorts, reps, shop products). Returns matching documents with title, url and excerpt. Use type to filter by content type (e.g. holiday, sc_resort, page, product).

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional post_type filter, e.g. 'holiday' or 'sc_resort'
limitNoMax results (default 10)
queryYesFree-text search query

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?

With no annotations supplied, the description carries the full burden, and it does disclose the return shape — matching documents with title, url and excerpt — which is genuinely useful for a read-only search tool. It omits ranking/relevance behavior, whether results are truncated, and any indication of what an empty result means.

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 sentences with no filler, and the capability statement with its content-type scope is front-loaded before the filtering hint. Every clause carries information the agent can act on.

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 three-parameter, annotation-free tool with no output schema, the description usefully names the returned fields and the content universe, which is the right compensation. It is still incomplete on the routing question — how this differs from the many targeted getters among its siblings — which matters given the overlap in scope.

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 schema already documents all three parameters, making 3 the baseline. The description adds slightly by giving extra `type` values ('page', 'product') beyond the schema's two examples, but adds nothing about query syntax, matching behavior, or how `limit` interacts with result quality.

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 specific verb and resource — searching Ski Club of Great Britain website content — and enumerates the content types covered (articles, holidays, ski tests, discounts, resorts, reps, shop products). It does not distinguish itself from siblings like find_resort, get_product, or search_help, which appear to overlap with the 'resorts' and 'shop products' scope named here.

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?

The only guidance is 'Use `type` to filter by content type', which is parameter instruction rather than when-to-use advice. There is no statement of when to prefer this general search over the more targeted siblings (find_resort, get_product, search_help), so an agent facing a resort or product lookup has no routing signal.

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