Skip to main content
Glama

Szukaj słów

search
Read-only

Find Polish keyword matches across archived articles, AI notes, photo descriptions, and ancient sources, returning ranked documents with verbatim passages; choose archive or library scope.

Instructions

Keyword full-text search (content is Polish – query in Polish; diacritics optional, prefix and fuzzy matching). scope='archiwum' (default) searches the website's articles, their AI notes and AI photo descriptions; scope='biblioteka' searches the public-domain library of ancient sources. Returns ranked documents with verbatim passages. For searching by meaning/concept use search_by_meaning.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaksymalna liczba wyników
queryYesSłowa do wyszukania, np. „Atlantyda Platon” albo „wapn kosci”
scopeNoarchiwum = artykuły strony; biblioteka = dawne dziełaarchiwum
sectionNoOgranicz do działu archiwum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuinely useful behavior: Polish-language corpus, optional diacritics, prefix and fuzzy matching, and ranked results with verbatim passages. It does not discuss result volume, pagination behavior beyond the limit default, or tie-breaking in ranking, so the added context is solid but not exhaustive 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?

Four dense sentences with the verb+resource front-loaded, followed by query-language guidance, scope definitions, return shape, and the sibling pointer. No filler, and each sentence carries information the agent needs.

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 4-parameter read-only search with no output schema, the description covers purpose, corpus, matching behavior, and return shape adequately. The remaining gap is the 'section' filter, whose valid values are undocumented in both the schema and the description, leaving an agent unable to use it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns a bump by adding query semantics the schema lacks (query in Polish, diacritics optional, prefix and fuzzy matching) and by expanding scope beyond the schema's one-line gloss into a concrete account of each corpus. The 'section' parameter remains opaque – neither schema nor description hints at valid values – which keeps it from a 5.

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?

"Keyword full-text search" names a specific verb and resource, and the description immediately explains what each scope searches (website articles, AI notes, photo descriptions vs. the ancient-source library). It also names the sibling it is not: "for searching by meaning/concept use search_by_meaning." An agent can distinguish this from search_by_meaning 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 Guidelines5/5

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

It gives an explicit alternative and the condition that selects it (meaning-based search → search_by_meaning), plus a default scope and what each scope covers, so scope selection is decided up front. The only minor omission is that it does not mention narrower siblings like find_in_article or read_article for drilling into a single document.

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