Skip to main content
Glama

Museum manuscripts

gj_museum
Read-onlyIdempotent

Search Ganjoor museum manuscripts by title or poet, retrieve manuscript details, or fetch a specific page image for research and reference.

Instructions

Browse Ganjoor museum manuscripts and scans (گنجینه): search, one manuscript's details, or one page image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gj_museum"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNoWith slug: one page slug, e.g. 'p0001'.
pageNoPage number.
slugNoManuscript slug from a search, e.g. 'nowras'.
queryNoSearch manuscripts by title or poet; empty lists the newest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this as read-only, open-world, idempotent, and non-destructive, so the safety profile is covered. The description adds that browsing includes three distinct retrieval modes, but it does not explain pagination behavior, result limits, or what happens when query and slug are both supplied.

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 definition is a single front-loaded sentence with no wasted wording. It efficiently lists the three supported operations after naming the resource.

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?

The tool is read-only with four optional, fully described parameters and no output schema. The description covers the main operation modes, though it could be more complete about how query, slug, and item combine or what search results contain.

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%, and the schema itself explains the roles of query, slug, item, and page with examples. The description does not add meaning beyond the schema, so the baseline of 3 is appropriate.

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 clear verb and resource (browse museum manuscripts and scans) and enumerates three modes: search, single-manuscript details, and single page image. It does not name or distinguish any sibling tool explicitly, so sibling-level clarity remains partial.

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 is implied by the mode list: search with a query, details with a slug, and a page image with slug plus item. There is no explicit when-to-use versus alternatives, no exclusions, and no guidance on what happens when parameters conflict.

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