Skip to main content
Glama

ADITUS Developer Portal MCP

Search ADITUS documentation

search_docs
Read-onlyIdempotent

Full-text search across API modules, endpoints (name, path, description) and the guides (Shop Micro Frontend agent contract, full documentation and overview; Guidelines; Webhooks). The reference is English; German search terms are understood as well (a generated language layer maps them onto the English vocabulary, e.g. 'aussteller' → exhibitor, 'gutschein' → voucher). Returns ranked hits with ids usable in get_endpoint / get_guide.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum hits (default 10)
queryYesSearch terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search terms, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token'"New value: +"Search terms in English or German, e.g. 'create cart', 'webhook signature', 'timeslot', 'session token', 'aussteller import'"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description adds real behavioral context beyond them: the reference corpus is English, German terms are mapped through a generated language layer (with a concrete 'aussteller' → exhibitor example), and results come back ranked.

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 sentences, front-loaded with the search scope and ending with the actionable return value. The parenthetical list of guide names is slightly verbose but does convey real coverage rather than filler.

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, read-only search with no output schema, the description covers scope, language handling, result shape (ranked hits with ids), and the follow-up path. Nothing needed to invoke it correctly is missing.

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 description coverage is 100%, so both query and limit are already documented in the schema, including the English-or-German note and examples. The description's language-mapping sentence adds only marginal semantics over that, so the baseline 3 applies.

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 (full-text search) and enumerates the exact corpora searched: API modules, endpoints (name, path, description), and named guides. It also distinguishes itself from list_endpoints/get_endpoint/get_guide by noting the returned ids feed those lookup tools.

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?

Implies the discovery-then-fetch workflow by saying ids are usable in get_endpoint / get_guide, which tells the agent when this tool is the entry point. It does not explicitly state when to prefer list_endpoints or list_modules over search, leaving that comparison to inference.

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