Skip to main content
Glama

Ask about a library's services

ask_library
Read-onlyIdempotent

Answers open-ended questions about a library's services, policies, or facilities by browsing the library's own website when standard catalogue and branch tools do not cover them.

Instructions

Answer an open-ended question about a library's services, policies or facilities by having a TinyFish Agent browse the library's own website. Use it for things the other tools do not cover, e.g. 'How do I get a card as a non-resident?', 'Can I book a study room at North York Central?', 'What are the overdue fines?'. Much slower than the other tools: a full answer usually takes 1 to 3 minutes. This call waits about 40 seconds; if the Agent is still working it returns status 'running' with a job_id, and you call get_job_result with that id until it is done.

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": {
      "question": "<question>"
    },
    "name": "ask_library"
  }
}

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.
questionYesThe question, in plain language. Name the branch if it is about one branch.

Output Schema

NameRequiredDescriptionDefault
foundYesFalse if the website does not state the answer.
answerYes
job_idYesSet while status is 'running'. Pass it to get_job_result.
sourceYesProvenance of the data.
statusYes
libraryYes
source_urlsYes
pages_consultedYesPages found by search and read before the Agent started.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, open-world, idempotent and non-destructive, and the description adds real operational context beyond them: a 1–3 minute typical answer time, a ~40 second synchronous wait, and the 'running' + job_id polling pattern. That is exactly the latency and continuation behavior an agent needs and annotations cannot convey.

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 sentences, front-loaded with purpose, then scope examples, then the timing/async caveat. No filler; the latency warning immediately follows the usage section where it is most decision-relevant.

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?

Even though an output schema exists, the description covers the one thing that schema cannot: that the response may be a pending job requiring polling. Combined with full parameter coverage and annotations, an agent has everything needed to invoke and follow up correctly.

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 'library' and 'question' are already documented with format and length constraints. The description adds illustrative question phrasing but no new semantics for the parameters themselves, so the baseline of 3 applies.

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?

States a specific verb and resource — answer an open-ended question about a library's services/policies/facilities by browsing the library's own website — and explicitly carves out territory from siblings ("things the other tools do not cover"). The concrete example questions make the intended scope unmistakable.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance with three representative questions, and names the fallback tool (get_job_result) plus the exact condition that triggers it (status 'running' with a job_id). It also warns that this is much slower than alternatives, which lets an agent choose against it when latency matters.

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