smoobu_list_price_elementsList the financial breakdown of one reservation: base price, cleaning fee, add-ons, long-stay discounts and coupons, with amounts, tax and currency. Smoobu: GET /api/reservations/{reservationId}/price-elements.
| Name | Required | Description | Default |
|---|---|---|---|
| reservation_id | Yes | The reservation (booking) id. |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, so the safety profile is already covered. The description adds that the response carries amounts, tax and currency, which is useful context, but it says nothing about pagination, currency conversion behavior, error cases for missing reservations, or line-item aggregation. A 3 fits given annotations carry the safety burden.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the verb and scope, followed by the concrete list of returned fields and the underlying API route. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description carries the return-value burden and does so by listing the breakdown components and their accompanying amounts, tax and currency. It is nearly complete for a single-reservation read; only edge behavior (missing id, empty breakdown) is unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single parameter is documented as 'The reservation (booking) id.' The description only restates that it operates on one reservation, adding no format or constraint detail beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List the financial breakdown of one reservation') and enumerates exactly what the breakdown contains (base price, cleaning fee, add-ons, discounts, coupons, tax, currency). This clearly distinguishes it from siblings like smoobu_get_reservation or smoobu_list_reservations without needing to open the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the phrasing 'of one reservation' - the agent can infer this is the per-reservation financial lookup - but no when-to-use condition, prerequisite, or alternative tool is named. It stops short of routing the agent between this and smoobu_get_reservation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.