Skip to main content
Glama

AnwaltX Passenger Rights & Legal Info (Germany/EU)

AnwaltX-Blog durchsuchen

search_legal_articles
Read-onlyIdempotent

Durchsucht die veröffentlichten Artikel im AnwaltX-Blog (u. a. Amazon-Seller-Probleme, DSGVO im Onlinehandel) nach Stichwort und liefert Titel, Kurztext und Link.

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

Input Schema

NameRequiredDescriptionDefault
queryYesStichwort, z. B. 'Section 3' oder 'DSGVO'

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond them by naming the returned fields (Titel, Kurztext, Link), which matters because there is no output schema. It stops short of describing result limits or pagination for a search tool.

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?

A single front-loaded sentence states the action, the corpus, an illustrative field list, and the return payload with no filler. Every clause earns its place.

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?

For a one-parameter search tool with full schema coverage, no output schema and annotations covering the safety profile, the description covers purpose and return fields adequately. The only gap is the absence of any note on result count or ranking behaviour, which is minor here.

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?

Only one parameter exists and schema description coverage is 100%, so the schema already fully documents 'query' with its own example. The description's phrase "nach Stichwort" merely restates the parameter, matching the baseline 3 for high-coverage schemas.

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?

The description gives a concrete verb ("Durchsucht") and a specific resource ("veröffentlichte Artikel im AnwaltX-Blog"), plus example topics (Amazon-Seller-Probleme, DSGVO im Onlinehandel) that pin down the domain. It does not explicitly contrast itself with siblings like lookup_legal_term or list_free_legal_templates, but the blog-article scope is narrow enough that an agent can separate it from the compensation calculators and template tools.

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

Usage Guidelines2/5

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

There is no statement of when this tool should be chosen over lookup_legal_term, list_free_legal_templates, or the calculators, and no stated prerequisites or exclusions. The only implicit guidance is the topic examples, which hint at the subject matter but not at tool selection.

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