Skip to main content
Glama

Get branch details

get_branch
Read-onlyIdempotent

Retrieve current details for one library branch—weekly hours, open status, holiday closures, services, accessibility, parking, and directions—by branch name or code.

Instructions

Everything about one branch: weekly hours, whether it is open now, upcoming holiday closures, services and facilities (meeting rooms, printing, makerspaces), accessibility, parking and directions.

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": {
      "branch": "<branch>"
    },
    "name": "get_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesBranch name or code, e.g. "Yorkville" or "YO".
libraryNoLibrary system id such as "tpl" (Toronto), "vpl" (Vancouver), "chipublib" (Chicago). Get it from find_library. A city or library name also works.

Output Schema

NameRequiredDescriptionDefault
branchYes
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 read-only, idempotent, open-world, non-destructive behavior, so the description need not restate safety. It adds value by specifying the breadth of returned branch information, but it does not disclose permissions, rate limits, or other behavioral caveats beyond that.

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 lists the relevant details without redundant phrasing or burying the scope. Every clause contributes to telling the agent what the tool returns.

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?

For a simple read tool, the description is complete enough: it identifies the resource, enumerates the returned data, and the schema/annotations/output schema cover parameters, safety, and return shape. The only notable contextual omission is explicit routing relative to sibling tools.

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?

The input schema has full description coverage for both branch and library, including examples and where to get library IDs. The description adds no parameter-level meaning, so the high schema coverage 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 names a specific resource ('one branch') and enumerates the data returned (weekly hours, open status, holiday closures, services, accessibility, parking/directions), making the tool's function clear. It does not explicitly name the sibling list_branches or otherwise state how it differs, so it falls short of 5.

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?

There is no explicit guidance on when to call get_branch versus list_branches, find_library, or other siblings. The phrase 'Everything about one branch' implies a single-branch detail lookup, but no prerequisites or alternatives are described.

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