rental_session_read
Read a bridge session: see all added properties, messages, and status.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| session | Yes | Session hash | |
| agent_id | No |
registry
TDQS
C2.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description minimally indicates a read operation but fails to disclose behavioral traits like read-only guarantee, authentication needs, rate limits, or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no extra words. However, it sacrifices completeness for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, incomplete schema documentation, and no output schema, the description is insufficient. It lacks information on return structure, error states, or usage constraints needed for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 50% (only 'session' has a description). The tool description adds no parameter meaning beyond 'see all added properties, messages, and status', which does not clarify 'agent_id' or how to format 'session hash'.
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 clearly states the tool reads a bridge session and displays added properties, messages, and status. It distinguishes from sibling tools like rental_session_add and rental_session_create by indicating a read operation, but does not explicitly differentiate.
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?
No guidance on when to use this tool versus siblings or other tools. No context about prerequisites or exclusions is provided.
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
A3.5/5.0
Disambiguation4/5
Most tools target distinct actions, but the presence of both 'search' and 'rental_search' could cause confusion, and 'fetch' overlaps slightly with 'rental_property'. However, descriptions clarify the differences.
Naming Consistency3/5
While most tools use a 'rental_' prefix, two tools ('fetch', 'search') lack it, and the naming style varies between verb-noun and noun-only (e.g., 'rental_availability' vs 'rental_search'). This inconsistency could confuse an agent.
Tool Count5/5
With 16 tools, the set covers a comprehensive range for a Caribbean rental assistant, including search, property details, pricing, availability, licensing, market intelligence, and session management. Each tool serves a clear purpose.
Completeness4/5
The tool set covers the core lifecycle (search, view details, create sessions, add picks), but lacks session update/delete functionality. Also, 'fetch' and 'search' seem redundant with rental-focused tools. Overall, the domain is well-covered for an agent workflow.