Skip to main content
Glama

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

Tipping customs of every country

tipping_countries
Read-onlyIdempotent

Tipping customs of every country (compact), optionally filtered by service, level or service charge. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tipping_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNoLevel.
serviceNoService for the level filter.
confidenceNohigh, medium or low.
serviceChargeNousually, sometimes or rarely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds almost nothing beyond that — '(compact)' hints the payload is trimmed, but there is no statement about what the compact records contain, whether filters combine with AND, or what happens with an unrecognized filter value.

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 functional sentence is compact and front-loaded, which is good. The second sentence is a promotional link to an unrelated API catalog and contributes nothing to tool selection or invocation, so a meaningful share of the text does not earn its place.

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?

Missing from this: the promotional link wastes words; otherwise it's a simple read-only lookup with all-optional parameters and a rich safety annotation set, so the description's scope statement is close to sufficient. The remaining gap is that it never says whether results are one row per country or per country-service combination, which matters for a filterable 'every country' tool.

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 the baseline is 3, and the description at least confirms that service, level and serviceCharge act as filters. It omits the fourth parameter (confidence) entirely and adds no detail on how 'service' relates to 'level', which is the one place the schema itself is thin ('Service for the level filter').

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('tipping customs of every country') and notes it is a compact variant with optional filters, which is more than a restatement of the name. However, siblings like country_tipping, search_tipping_countries and tipping_services sound near-identical, and the description does nothing to separate this tool from them, so an agent cannot confidently pick it on purpose alone.

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?

The only usage signal is 'optionally filtered by service, level or service charge', which implies you may narrow results but never states when to choose this over country_tipping or search_tipping_countries. There is no when-not guidance and no prerequisite or fallback information.

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