Skip to main content
Glama

get_business_location

Read-onlyIdempotent

Read a business location by ID, including its staff assignments and whether it is offered for booking.

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": {
      "id": "<id>"
    },
    "name": "get_business_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive semantics, so the safety profile is covered. The description adds useful payload context that annotations cannot convey: the read returns staff assignments and whether the location is bookable. Missing are not-found/error behavior and any permission notes.

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 no wasted wording; the verb, resource, lookup key, and return contents are all packed into one clause.

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 one-parameter read tool with full annotation coverage and no output schema, the description is close to sufficient: it names the key and summarizes the returned fields. It could still mention behavior when the ID is unknown or whether a partial/error response is possible.

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 0%, so the description must carry the parameter meaning, and it only says 'by ID'. The schema does supply format=uuid and a strict pattern, which makes the identifier self-explanatory, but the description adds no format, source, or lookup guidance beyond the word 'ID'.

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 ('Read a business location by ID') and adds what the response includes (staff assignments, booking availability), which distinguishes it from a bare name restatement. It does not explicitly distinguish itself from list_business_locations or save_business_location, but the read-by-ID scope is unambiguous.

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?

The 'by ID' phrasing implies the tool is for fetching one already-identified location, while list_business_locations would be used to discover IDs. However, no alternative is named and there are no exclusions or prerequisites stated, so guidance is only implied.

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.

Resources