Skip to main content
Glama

Search guides, blog and products

search_content
Read-onlyIdempotent

Keyword search over Klarframe product pages, guides (Ratgeber) and blog articles. Returns titles, URLs and a matching sentence. Covers topics such as AI phone assistants, meeting minutes, EU AI Act Article 50, GDPR and costs of AI models.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: de, en, es or it. Defaults to de.de
limitNo
queryYesSearch words, any of the four languages

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 the safety profile is covered. The description adds genuinely new behavioral context: the exact return shape (titles, URLs, a matching sentence) and the scope of the indexed corpus, which annotations cannot express. It omits ranking/pagination behavior and what happens with cross-language queries, keeping it at 4.

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, zero filler. The search scope and corpus lead, followed by the return shape and topic coverage; every clause carries information an agent can act on.

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 no output schema, the description correctly takes on the burden of describing return values (titles, URLs, matching sentence) and corpus boundaries. The main residual gap is the interaction between lang and results, and relevance ordering, which matter for a search tool but are secondary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description adds no parameter-level meaning at all: it never mentions lang, its default of de, or limit and its 1-10 cap. The corpus topic list describes content, not parameters. With the schema only partially documented, the description needed to compensate and does not.

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?

"Keyword search over Klarframe product pages, guides (Ratgeber) and blog articles" gives a specific verb (keyword search) and a precisely enumerated corpus, which is enough to separate it from list_products or get_product by name alone. It stops just short of explicitly naming that contrast, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. The listed topic examples (AI phone assistants, meeting minutes, EU AI Act Article 50) do implicitly tell the agent what kind of question this tool answers, but selecting it over list_products or company_info is left 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