Skip to main content
Glama

Search the website

search_site
Read-onlyIdempotent

Keyword search across the whole Almost Impossible website: pages, case studies, news and journal articles. Start here for any open question ("experiential work for banks", "pricing", "awards"). Returns up to 10 matches with URL and summary; read one in full with get_page.

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_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches to return, from 1 to 10.
queryYesWhat to look for, in a few words.

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds useful behavior beyond that: the result cap of 10, and the fact that matches carry a URL and a summary rather than full text. It stops short of saying how results are ranked or whether page bodies are indexed, which keeps it off a 5.

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?

Three short sentences, zero filler, and the scope statement is front-loaded before the examples and the next-step pointer. Each sentence carries distinct information: what it searches, when to reach for it, and what to do with results.

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

Completeness5/5

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

For a simple two-parameter search tool with full schema coverage, rich annotations and an output schema, nothing an agent needs is missing: scope, trigger conditions, result shape, and the follow-up tool are all stated. Return-value details are correctly left to the output schema rather than duplicated.

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 coverage is 100% and both parameters are documented, so the baseline is 3. The description earns an extra point by supplying example query strings that demonstrate the expected keyword phrasing, which is more actionable than the schema's 'a few words in length' note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Keyword search across the whole Almost Impossible website') and enumerates the content types covered: pages, case studies, news and journal articles. An agent can immediately tell this apart from retrieval siblings like get_page or list_work without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'Start here for any open question' and gives concrete query shapes ('experiential work for banks', 'pricing', 'awards'). It also names the follow-up alternative: 'read one in full with get_page', so the search-then-fetch workflow is unambiguous.

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