Skip to main content
Glama

NS Pros MCP Gateway

nplg-catalog__nplg_dlibrary_search

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-catalog__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
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does useful work by disclosing the shape of a hit (authors, issue date, source citation, multilingual subject headings, Dewey class, stable URL) and the fixed page size of 10. It says nothing about ranking/relevance, matching semantics (exact vs. phrase vs. stemmed), rate limits, authentication, or behavior on empty results, which leaves meaningful gaps for a no-annotation 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?

Three short sentences, front-loaded with what the collection is, followed by what a result contains and then the pagination constant. Every sentence contributes distinct information with no restatement of the name or padding.

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?

With no output schema in play, the description supplies the return-field inventory an agent needs to decide whether to call it, and the paging constant is stated. Remaining gaps are relevance ranking and matching semantics, which matter for a search tool but are secondary to deciding whether to invoke 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 description coverage is 100%, so all three parameters are already documented, and the enum values appear in the description only as the collection list already present in the schema. The phrase 'Pages 10 at a time' reinforces the fixed page size beyond the schema's '1-based page number; the page size is 10,' but adds little else about query syntax or script handling.

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?

States a specific verb and resource ('Search the digital library of the National Parliamentary Library of Georgia') and narrows scope to a 'small full-text collection of scanned print archive, dissertations and posters.' An agent can tell it is a bibliographic full-text search, though the description never names or contrasts it with the sibling nplg_search, so sibling differentiation is left implicit.

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?

Usage context is implied by the collection description (print archive, dissertations, posters) rather than stated. There is no explicit when-to-use rule, no mention of when another search tool in the catalog would be preferable, and no prerequisites or exclusions called out.

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.