Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

How much to tip

tip_amount
Read-onlyIdempotent

How much should I tip at a restaurant, taxi, hotel or for a guide in a country? The custom and, with a bill amount, the tip to leave. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "country": "<country>",
      "service": "<service>"
    },
    "name": "tip_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsNoNights (hotel) or person-days (guide), 1-365 (default 1).
amountNoThe bill or fare, a plain number (48.50, 5000). Needed for percent and round-up customs.
countryYesISO code or name.
serviceYesrestaurant, taxi (rideshare, uber, cab), hotel (housekeeping) or guide (tour).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already cover safety and side-effect behavior (read-only, non-destructive, idempotent, not open-world). The description adds that the tool returns the custom and, when an amount is supplied, the tip to leave, but it does not describe the response shape or handling of missing optional inputs beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the core question, but the final sentence promoting other APIs from FitzTopPicks does not help an agent select or invoke this tool. Removing that marketing line would make the definition tighter.

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 simple four-parameter read-only tool with a fully described schema and no output schema, the description is mostly complete: it explains the main use case and the conditional tip calculation. It does not mention the optional 'units' parameter or give detail on the returned structure, but those gaps are partly covered by the schema and annotations.

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 100%, so all four parameters are already documented in detail, including units, amount, country, and service. The description reinforces the service types and bill-amount use case but adds no syntax, constraints, or meaning beyond what the schema already provides.

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 makes clear it answers how much to tip for restaurant, taxi, hotel, or guide services in a given country, and it mentions both customary guidance and a calculated tip when a bill amount is provided. The purpose is specific, but it does not distinguish this tool from the sibling 'country_tipping'.

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 gives a clear usage context: tipping in a country for restaurant, taxi, hotel, or guide services, with optional bill amount for calculating the tip. It does not state when not to use it or name any alternative sibling, so it falls short of explicit routing guidance.

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