Skip to main content
Glama

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

Tipping customs of a country

country_tipping
Read-onlyIdempotent

Tipping customs of a country (by ISO code or name) for restaurants, taxis, hotels and guides, and whether a service charge is usual. 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": {
      "code": "<code>"
    },
    "name": "country_tipping"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesISO code or country name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the side-effect profile is fully covered by structured data. The description's only added behavioral value is enumerating the returned content categories and the service-charge flag, which is genuinely useful since no output schema exists. It says nothing about response shape, unknown-country behavior, or data freshness.

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 first sentence is front-loaded and information-dense, covering resource, key, and returned categories efficiently. However, the trailing promotional sentence about 'More APIs from FitzTopPicks' with UTM parameters consumes roughly a third of the text and provides zero selection or invocation value.

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 single-parameter read-only lookup this is close to complete: it names the input form, the categories returned, and the service-charge dimension. Since no output schema exists, the enumeration of return categories carries the needed weight. Minor gap: nothing about countries not covered or error behavior.

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 coverage is 100% and the single `code` parameter already documents 'ISO code or country name.' The description's parenthetical '(by ISO code or name)' merely restates the schema, adding no format or casing detail. Baseline 3 is appropriate when the schema does the work.

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 gives a specific resource (tipping customs for a country) plus the covered categories (restaurants, taxis, hotels, guides) and the service-charge question, so an agent knows exactly what domain this answers. It does not mention or distinguish itself from likely siblings such as tipping_countries or search_tipping_countries, so it falls short of a 5.

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?

Usage is implied: look up a single country by ISO code or name to get its tipping norms. There is no statement about when to prefer this over the list/search siblings, nor any prerequisite or failure guidance (e.g. unknown country). Adequate but leaves routing to inference.

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