Skip to main content
Glama

Szukaj po znaczeniu

search_by_meaning
Read-only

Finds passages by meaning rather than exact words across Polish and English archive and library sources, returning matching passages with article or book IDs.

Instructions

Semantic search: finds passages whose MEANING matches the query, even if they use different words (e.g. 'katastrofy z kosmosu' finds texts about comets, Tiamat, meteorites). Works in Polish and English. scope: 'archiwum' (articles, AI notes, AI photo descriptions), 'biblioteka' (ancient public-domain sources) or 'wszystko'. Returns the best matching passages with their article/book ids.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesPytanie lub opis tematu, np. „czy dawne cywilizacje znały energię atomową”
scopeNoarchiwum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: bilingual operation (Polish and English), what each scope contains, and the return shape ('best matching passages with their article/book ids'). It omits ranking/limit behavior and any notes on result quality or pagination, keeping it short of a 5.

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 the core definition, then scope and returns — a sensible order with no filler. The example and language note both earn their place, though the single dense paragraph could be split for scanability.

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 3-parameter read-only search with no output schema, the description covers purpose, scope semantics, languages, and return content — enough to invoke correctly. The only real gap is the unexplained limit parameter.

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 low (33%) — only 'query' is documented in the schema. The description compensates well for 'scope' by spelling out all three enum values and their contents ('archiwum', 'biblioteka', 'wszystko'), but says nothing about 'limit' (1-30, default 10) or how the query string is interpreted. Partial compensation warrants the baseline 3.

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-like operation and resource ('Semantic search: finds passages whose MEANING matches the query') and immediately differentiates itself from keyword matching with a concrete Polish example ('katastrofy z kosmosu' finds comets, Tiamat, meteorites). An agent can tell this apart from the sibling 'search' tool without opening either schema.

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

Usage Guidelines4/5

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

The phrase 'even if they use different words' clearly signals the semantic-vs-keyword split that selects this tool over the plain 'search' sibling, and the scope values give clear context on coverage. However, it never names an alternative explicitly nor states when not to use it (e.g. exact-phrase lookups).

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