Skip to main content
Glama

add_price

Add a season price to a boat the operator prices directly (pricing source direct). Returns the stored row.

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": "<name>",
      "start_month": "<start_month>",
      "start_day": "<start_day>",
      "end_month": "<end_month>",
      "end_day": "<end_day>",
      "price_per_day": "<price_per_day>"
    },
    "name": "add_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBoat id, from list_boats.
nameYesSeason name.
end_dayYes
priorityNoThe higher one wins where two seasons overlap.
end_monthYes
start_dayYes
start_monthYes
price_per_dayYesEUR per day for the boat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations declare this is a non-destructive write (readOnlyHint=false, destructiveHint=false), and the description adds two things structured fields don't: the return behavior ('Returns the stored row') and the applicability constraint (direct pricing source). It stops short of documenting failure modes or auth requirements.

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?

Two tight sentences with the action front-loaded and zero filler. Every clause carries information (scope, applicability, return).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with 50% schema coverage and no output schema, the description covers purpose and return shape but leaves the date fields and priority semantics unexplained. Adequate but with clear gaps.

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 coverage is only 50%; the four date fields (start_month/day, end_month/day) have no description in either schema or description. The prose adds no syntax, format, or meaning beyond the word 'season', so it fails to compensate for the coverage gap.

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 (Add) and resource (season price to a boat), plus a scoping qualifier (pricing source direct). It's clearly distinct from get_pricing/delete_price, but it never explicitly contrasts with the sibling update_price, so an agent must infer the boundary.

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 parenthetical '(pricing source direct)' implies a precondition for use, which is better than nothing, but there is no explicit when-not and no named alternative such as update_price for adjusting an existing season row. Usage 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.