Skip to main content
Glama

Nusa Penida Holiday Planner

Reise-Insights & Geheimtipps aus deutschen Blogs

search_blog_insights
Read-onlyIdempotent

Durchsucht kuratierte Insights aus deutschen Reiseblogs mit Freitext, Multi-Tag und Blog-Quelle.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoListe von Tags, alle müssen im Eintrag vorkommen.
limitNoTrefferzahl (1-50, default 20).
queryNo
offsetNoOffset für Pagination (0-500, default 0).
sort_byNo
source_blogNoBlog-Domain, z.B. 'indojunkie.com', '22places.de'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is known. The description adds the relevant domain constraint that the corpus is a curated set of German travel blogs, which is real context beyond the annotations, but says nothing about match semantics across facets, result shape, or paging behavior.

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 tight sentence with no filler, front-loading the resource being searched and then the supported facets. Nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six optional parameters and no output schema, the description could usefully say what a result contains and how empty/partial queries behave. It covers the search surface adequately but leaves an agent guessing about return content and result ordering.

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 67%, with tags, limit, offset, and source_blog already documented (including the AND semantics for tags and the domain example). The description restates the three main facets but adds no syntax, default, or matching behavior beyond the schema; limit, offset, and sort_by are left entirely to the schema.

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 uses a specific verb ("Durchsucht") and a precise resource ("kuratierte Insights aus deutschen Reiseblogs") and names the three searchable facets: free text, multiple tags, and blog source. This clearly separates it from generic listing siblings like list_travel_tips, though it never explicitly names an alternative.

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 to use this tool versus the other search/list siblings, no prerequisites, and no exclusions (e.g. whether it covers only German-language blogs or curated versus crawled content). Usage is only inferable from the tool's name and the enumerated facets.

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