Skip to main content
Glama

Achriom

by com.achriom.mcp
OverviewDiscussionsAdmin

Search library by meaning

search_library
Read-onlyIdempotent

Semantic search across the user's entire library by meaning, theme, or vibe. Searches every book/movie/album/show/anime/podcast/game as one corpus. Use for cross-media or thematic questions like "things about grief" or "noir mood", or any generic/conceptual query where the exact wording may not appear in the item's title/creator/genre text. For specific title/creator lookups, use the keyword search tool instead.

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 25)
queryYesNatural-language description of what to find (theme, mood, idea, vibe)
media_typeNoOptional filter to a single media type
min_similarityNoCosine similarity floor 0–1 (default 0.20). Lower for mood/affect queries (e.g. "something slow and quiet" → 0.15), higher for specific-entity queries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / media_type / enum
      Previous value: -[
-  "book",
-  "movie",
-  "album",
-  "show",
-  "anime"
-]New value: +[
+  "book",
+  "movie",
+  "album",
+  "show",
+  "anime",
+  "podcast",
+  "game",
+  "manga"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / min_similarity / description
      Previous value: -"Cosine similarity floor 0–1 (default 0.3)"New value: +"Cosine similarity floor 0–1 (default 0.20). Lower for mood/affect queries (e.g. \"something slow and quiet\" → 0.15), higher for specific-entity queries."
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds meaningful behavioral context beyond that: search is semantic rather than literal, spans every media type as one corpus, and is intended for conceptual queries where exact wording may not appear. It does not describe result ordering or pagination, but the schema covers the limit and similarity floor.

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?

The description is three tight sentences with no waste. The scope and primary use case are front-loaded, followed immediately by the sibling distinction.

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 read-only semantic search tool with full schema coverage and no output schema, this description contains everything needed to select and invoke it correctly: purpose, corpus scope, query style, examples, similarity tuning context in the schema, and the alternative keyword tool.

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 each parameter is already documented. The description illustrates the kind of natural-language query to pass but does not add syntax, format, or parameter-specific guidance beyond what the schema provides. Baseline 3 is appropriate.

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?

The description states a specific verb and resource: semantic search across the user's entire library by meaning, theme, or vibe. It distinguishes this from the sibling `search` tool by explicitly contrasting meaning-based search with keyword lookups.

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?

It gives explicit usage guidance with examples such as "things about grief" and "noir mood", and it names the alternative for specific title/creator lookups: the keyword `search` tool. The conditions for choosing this tool versus that sibling are clear.

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

All Achriom toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources