Skip to main content
Glama

Get title details

get_title
Read-onlyIdempotent

Retrieve complete details for a single library title using its title_id, including description, contributors, publisher, ISBNs, subjects, series, and all held formats.

Instructions

Full details for one title: description, contributors, publisher, ISBNs, subjects, series, and every other format the library holds it in.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title_id": "<title_id>"
    },
    "name": "get_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
libraryNoLibrary system id such as "tpl" (Toronto), "vpl" (Vancouver), "chipublib" (Chicago). Get it from find_library. A city or library name also works.
title_idYesA title_id from search_catalog, e.g. "S234C3970025".

Output Schema

NameRequiredDescriptionDefault
titleYes
sourceYesProvenance of the data.
libraryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description's help. The description adds real value by disclosing the breadth of the payload, including 'every other format the library holds it in', which tells the agent to expect a large response. It says nothing about permissions, rate limits, or failure behavior for an invalid title_id.

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?

A single front-loaded sentence with the resource identified immediately and the field enumeration serving a real purpose: it tells the agent what this returns versus a search result. No filler or redundant restatement of the title.

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?

An output schema exists, so return-value structure need not be explained, and annotations cover safety; the description correctly focuses on scope and breadth of detail. With 100% schema coverage and only two parameters, the only meaningful gap is the absent cross-reference to search_catalog/find_library as prerequisites.

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 both parameters (title_id provenance, library system id with examples and find_library pointer) are already fully documented in the schema. The description adds no parameter-level meaning such as format expectations or what happens when library is omitted, so baseline 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?

States a specific verb and resource ('Full details for one title') and enumerates the content returned: description, contributors, publisher, ISBNs, subjects, series, and other formats. This reads clearly as a detail-expansion tool rather than a search, though it never names search_catalog as the discovery counterpart, so sibling differentiation is inferred rather than stated.

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 guidance and names no alternative tool. It doesn't say this should follow a search_catalog hit or that it is the wrong tool for browsing a collection; that provenance chain ('A title_id from search_catalog') lives only in the schema, not the description.

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