Skip to main content
Glama

Search the i22 website

i22_ai_site_search
Read-onlyIdempotent

Full-text search over the published pages of the i22 website. Returns matching pages with title, URL and short description. Terms are OR-linked; use a few precise words (at most 200 characters). Read a hit with i22_ai_page_read before answering from it. Retrieval needs no personal data; do not include any in queries.

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

Input Schema

NameRequiredDescriptionDefault
queryYesSearch words.
localeNoLanguage of the content: "de" (default) or "en".de

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real substance beyond them: OR-linked term matching (which explains result breadth), the returned fields (title, URL, short description) in the absence of an output schema, and a privacy constraint that queries need no personal data.

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?

Four short sentences, front-loaded with what the tool is, followed by query semantics, the required follow-up read, and the privacy rule. Nothing is padded and no sentence repeats the name or title.

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 two-parameter, annotation-backed search tool with no output schema, the description covers the corpus, result shape, matching semantics, length limit, privacy constraint, and next-step workflow. An agent can call it correctly and knows what to do with a hit.

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%, so the baseline is 3; the description earns an extra point by explaining that terms are OR-linked and that the 200-character cap is best met with a few precise words, which is behavioral meaning the schema's "Search words." does not convey. The locale parameter's effect is left entirely to the schema.

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?

"Full-text search over the published pages of the i22 website" names a specific verb (full-text search) and a specific corpus (published website pages), which cleanly separates it from siblings like i22_ai_page_list (enumeration) and i22_ai_cases_find (case records).

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

Usage Guidelines4/5

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

The description states a querying discipline ("use a few precise words") and an explicit follow-up route: read a hit with i22_ai_page_read before answering from it. What it lacks is an explicit statement of when to prefer this over the sibling finders, so a 4 rather than a 5.

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