Skip to main content
Glama

Nplg Search

nplg_search
Read-onlyIdempotent

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 time via offset.

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_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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the bar is lower. The description still adds real value: it promises the true total match count as well as the current page, fixes the page size at 50, and specifies which fields each citation carries.

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?

Four sentences, front-loaded with the resource and return shape, then script support, scope, and paging in descending order of importance. Slightly dense but no sentence is filler.

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?

With no output schema, the description carries the return-value burden and does so fully: total count, page of citations, and the exact fields (bib id, Georgian title with parallel Latin title, author, imprint, material type). An agent has everything needed to call and interpret it.

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 the baseline is 3; the description restates the script flexibility and repeats the 50-record page size and scope narrowing that the schema already documents. It adds only marginal meaning beyond the structured fields.

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 names a specific verb and resource ("Search the union catalogue of the National Parliamentary Library of Georgia") and lists the searchable indexes (keyword, title, author, subject). The phrase "union catalogue" implicitly separates it from the sibling digital-library search without requiring the agent to open another schema.

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

Usage Guidelines3/5

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

It supplies practical usage context — queries work in Georgian (მხედრული) or Latin script, scope narrows by material, offset pages results — but never states when to prefer this tool over nplg_dlibrary_search or other search siblings, nor any exclusions.

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.