Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__nplg_search

Search the union catalogue of the National Parliamentary Library of Georgia by keyword, title, author or subject. Returns the true number of matching records alongside the page of citations, each with its permanent bib id, title (Georgian with a parallel Latin title where the record carries one), author, imprint and material type. Queries work in Georgian (მხედრული) or Latin script. Narrow by material with scope (books, periodicals, maps, dissertations, archival documents...). Pages 50 at a ti

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "tbilisi"
    },
    "name": "nplg-catalog__nplg_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoWhich index to search: keyword (default), title, author, subject.
queryYesSearch terms. Georgian or Latin script both work; "and"/"or"/"not" are honoured.
scopeNoMaterial scope, 1-11. 1 = entire collection (default), 2 books, 3 periodicals, 4 posters and prints, 5 cartographical, 6 electronic, 7 dissertations, 8 music and audio, 9 archival documents, 10 newspaper articles, 11 journal articles.
offsetNoZero-based record offset for paging; the page size is 50. Pass 50 for the second page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses the return payload (true match count plus a page of citations with bib id, Georgian/Latin title, author, imprint, material type) and the page size of 50. It says nothing about authentication, rate limits, or empty-result behavior, and the final paging sentence is cut off mid-word.

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?

Dense and front-loaded: purpose first, then return shape and script support, then the scope and paging notes. The one blemish is the truncated trailing clause ('Pages 50 at a ti'), which leaves an unfinished sentence in the definition.

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 four-parameter read-only search with no output schema and no annotations, the description supplies the essentials an agent needs: what is searchable, what comes back, script compatibility, material scoping and pagination. Authentication, error handling and the truncated paging tail are the remaining gaps.

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 the baseline is 3; the description only reinforces what the schema already states, restating the material-scope idea with a partial list of scope examples that does not fully match the schema's 1-11 enumeration. It adds no format or edge-case detail for `index` or `offset` beyond 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 opens with a specific verb and resource ('Search the union catalogue of the National Parliamentary Library of Georgia') and enumerates the searchable indexes (keyword, title, author, subject), so an agent immediately knows what the tool does. It does not explicitly name sibling tools such as nplg_record_marc or nplg_dlibrary_search to differentiate itself, which keeps it below a 5.

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?

It gives clear operating context: search in Georgian or Latin script, narrow by material via `scope`, and page via offset. What is missing is any explicit when-not or alternative routing (e.g. when to prefer the dlibrary or MARC record sibling), so the agent must infer which catalogue tool fits.

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.