Biohacking Kompakt

Themen auf Biohacking Kompakt suchen

bk_search_topics

Read-onlyIdempotent

Sucht in allen Themen von biohackingkompakt.de - Supplements, Peptide und experimentelle Substanzen, Anwendungen und Therapien, Biohacking-Tipps und Khavinson-Bioregulatoren. Durchsucht Namen, Zweitnamen, Schlagworte und Beschreibungstexte; Umlaute und Schreibweisen sind egal.

Liefert je Treffer eine Kurzfassung mit dem BK-Score. Fuer den vollstaendigen Eintrag mit Einnahme, Belegen, Risiken, Anwenderberichten und haeufigen Fragen danach bk_get_topic mit der zurueckgegebenen id aufrufen. Fuer Fragen, deren Antwort im Fliesstext irgendeiner Seite steht, bk_search_inhalte.

Args:

query (string): Suchbegriff, 2-120 Zeichen
bereich ('supplement' | 'experimental' | 'behandlungen' | 'tipps' | 'khavinson'): optionale Einschraenkung
limit (number): 1-50, Standard 10
offset (number): fuer weitere Seiten
response_format ('markdown' | 'json')

Returns: { total, count, offset, items: [{ id, view, name, bereich, kurz, score_label, evidenz, richtung, url }], has_more, next_offset }

Beispiele:

"Was steht bei euch zu Kreatin?" -> query="Kreatin"
"Welche Peptide zum Abnehmen habt ihr?" -> query="Abnehmen", bereich="experimental"
Nicht benutzen fuer: eine Podcastfolge finden (dafuer bk_search_podcast).

Input Schema

Name	Required	Description	Default
`limit`	No	Hoechstzahl der Treffer (1-50)
`query`	Yes	Suchbegriff, z. B. 'Kreatin', 'Schlaf', 'GLP-1', 'Löwenmähne'
`offset`	No	Wie viele Treffer uebersprungen werden
`bereich`	No	Auf einen Bereich einschraenken: supplement, experimental (Peptide), behandlungen, tipps, khavinson
`response_format`	No	Ausgabeformat: 'markdown' zum Lesen, 'json' zum Weiterverarbeiten	markdown

Output Schema

Name	Required	Description
`count`	Yes	Zahl der Eintraege in dieser Antwort
`items`	Yes	Die gefundenen Themen
`total`	Yes	Gesamtzahl der Treffer
`offset`	Yes	Wie viele uebersprungen wurden
`has_more`	Yes	Ob es weitere Treffer gibt
`next_offset`	No	offset fuer die naechste Seite

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, and the description adds the useful trait that umlauts and spelling are normalized. It also documents the shape of each hit (Kurzfassung with BK-Score). Return structure is largely covered by the output schema, so it needn't go further.

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?

Front-loaded with scope and fields searched, then follow-up routing and examples. Slightly long but every section earns its place; the examples in particular add real disambiguation value.

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?

Complete for a search tool: scope, searched fields, normalization behavior, result shape, pagination parameters, routing to detail and full-text siblings, and an explicit exclusion. Nothing an agent needs 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 coverage is 100%, so parameters are fully documented in the schema itself. The description adds interpretive value via examples (e.g., bereich='experimental' for peptides) but nothing beyond that. 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 (Sucht) and resource (Themen von biohackingkompakt.de), enumerates the covered content areas, and explains what fields are searched. It also distinguishes itself from bk_search_inhalte and bk_search_podcast by name.

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

Usage Guidelines5/5

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

Explicitly routes: use bk_get_topic with the returned id for the full entry, use bk_search_inhalte for full-text questions, and don't use for podcast episodes (use bk_search_podcast). Includes worked examples mapping natural-language questions to arguments.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Biohacking Kompakt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.