fetch
Fetch full details for one business id returned by search: services, hours, timezone and how to book it.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
g-guest
by app.g-guest
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, and it conveys that this is a read operation that returns details like services, hours, timezone, and booking information. It does not address errors, permissions, or edge cases, but 'Fetch' and the listed output make the general behavior transparent.
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?
One concise sentence, no wasted words, and the main action plus output categories are front-loaded. The description is easy to scan and understand.
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 tool with one required parameter and no output schema, the description covers the core need: what id to supply and what details will be returned. It could mention error behavior or explicitly confirm no side effects, but it is largely complete for this simple tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/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 compensate. It does by clarifying that the id parameter is a 'business id returned by search', telling an agent where the value comes from. It omits format or validation details, but for a single simple parameter this is adequate.
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 ('Fetch full details') and a specific resource ('one business id returned by search'), and lists concrete content categories: services, hours, timezone, and how to book. It does not explicitly distinguish itself from the sibling get_business, which keeps it from a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly frames usage as the follow-up to a search, using an id returned by search. It provides practical context but does not mention alternatives or when not to use this tool.
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.
TDQS
A4/5.0
Disambiguation3/5
check_availability, create_booking, and search are clearly distinct, but fetch and get_business overlap heavily: both retrieve business details, differing only by whether you have an id or a slug. An agent could confuse one for the other and still get largely the same information.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern: check_availability, create_booking, get_business. However, fetch and search are bare verbs that do not include their object, which is a minor deviation from the otherwise consistent style.
Tool Count5/5
Five tools is well-scoped for a booking-focused server. Each tool maps to a distinct step in the business discovery and reservation flow without unnecessary duplication or bloat.
Completeness4/5
The core guest journey is covered: search for a business, retrieve details, check availability, and create a booking. Missing booking lookup or cancellation tools are notable gaps, but they are not required for the primary make-a-reservation workflow.