Skip to main content
Glama

Nplg Dlibrary Search

nplg_dlibrary_search
Read-onlyIdempotent

Search the digital library of the National Parliamentary Library of Georgia, a small full-text collection of scanned print archive, dissertations and posters. Each hit carries authors, date of issue, a full source citation, subject headings in Georgian, Russian and English, a Dewey subject and a stable item URL. Pages 10 at a time.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number; the page size is 10.
queryYesSearch terms. Georgian or Latin script both work.
collectionNoWhich collection to search: all (default), print_archive, dissertations, posters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With annotations already declaring readOnly, openWorld, idempotent, and non-destructive behavior, the description adds useful context: what each hit contains (authors, date, citation, multilingual subject headings, Dewey, stable URL) and that results are paginated 10 at a time. It omits details like authentication or rate limits, but covers the key behavioral traits an agent needs for this read-only search.

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 two sentences, front-loaded with the resource and scope, then the result shape and pagination. Every sentence adds value without repetition or filler.

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?

There is no output schema, so the description helpfully enumerates the key fields returned by each hit and notes pagination. Combined with the fully documented input schema and read-only annotations, this is nearly complete for a search tool, lacking only explicit sibling-routing guidance.

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 schema already documents query, page, and collection semantics. The description's 'Pages 10 at a time' restates the page-size detail already present in the schema, adding little meaning beyond it.

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 states a specific verb and resource: searching the National Parliamentary Library of Georgia's digital library full-text collection, including its scope (scanned print archive, dissertations, posters). It is clear what the tool does, but it does not explicitly distinguish itself from the sibling nplg_search or nplg_record_marc.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use or when-not-to-use guidance. It implies full-text searching of the digital library, but does not tell an agent how to choose between this, nplg_search, or the individual collections beyond the enum in the schema.

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.