Skip to main content
Glama

Find case studies of i22

i22_ai_cases_find
Read-onlyIdempotent

Finds case studies of i22, optionally filtered by service, customer and free text; each with title, customer, service, in use since and teaser where the page has one. Use it for references and examples. The content has no industry field: for an industry, filter by customer or put the industry in query. Retrieval needs no personal data; do not include any in queries.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text search words.
serviceNoSlug (e.g. agentic-transformation), path or URL of a service from i22_ai_services_list.
customerNoPart of the customer name, e.g. Telekom.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real context beyond that: the exact return fields, the absence of an industry facet, and a privacy constraint warning against putting personal data in queries. Pagination or result-count limits are not mentioned.

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

Conciseness4/5

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

Three compact sentences, front-loaded with the core action and result shape before the filtering caveat and the privacy note. Every clause carries information; density is high but nothing is redundant.

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?

With three optional parameters and no output schema, the description compensates by enumerating the returned fields and clarifying the one missing facet (industry). Only the combination semantics of the filters and any result-limit behaviour are left unstated.

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 all three parameters are already documented, which sets the baseline at 3. The description does add meaning about the query parameter (industry terms can be substituted for the missing industry field) and points at i22_ai_services_list for service slugs, but says nothing about how multiple filters combine.

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?

States a specific verb and resource ("Finds case studies of i22") plus the filter dimensions and the fields returned, so an agent knows exactly what this retrieves. The resource is narrow enough to be distinguished from siblings like page_search or page_list without opening their schemas.

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?

Gives an explicit use case ("Use it for references and examples") and a workaround when the natural filter is unavailable: since there is no industry field, filter by customer or fold the industry into query. It also routes to i22_ai_services_list for service slugs. It stops short of naming when to prefer a sibling tool instead.

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