Skip to main content
Glama

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

Find countries by tipping custom

search_tipping_countries
Read-onlyIdempotent

Find countries by name, or by how tipping works there (e.g. where tipping is not expected at restaurants). 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": "search_tipping_countries"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName, code or alias.
levelNoexpected, customary, appreciated, not-expected or avoid.
limitNo1-100 (default 20).
serviceNoService the level filter applies to (default restaurant).
confidenceNohigh, medium or low.
serviceChargeNousually, sometimes or rarely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive reads, so the safety profile is covered. The description adds little beyond that — it does not say whether filters combine with AND semantics, what happens when no country matches, or whether results are paginated by the 'limit' parameter. The trailing promotional URL contributes nothing behavioral.

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 well front-loaded and earns its place, but roughly half the text is a marketing link to the author's API catalog, which does not help an agent select or invoke the tool. Removing it would leave a tight, focused definition.

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 a six-parameter, all-optional, read-only search with full schema coverage and no output schema, the description is adequate but thin: it never indicates what a result actually contains (country plus tipping levels per service?) or how multiple supplied filters interact. An agent can call it, but must discover the response shape empirically.

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%, including enum values and the 'service the level filter applies to' semantics, so the schema does the heavy lifting and the baseline is 3. The description's example implicitly shows that 'level' is meaningful per-service, which is a mild reinforcement, but it adds no syntax or combination rules beyond the schema.

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 verb and resource — find countries — and broadens it to retrieval by tipping behavior, with a concrete example ('where tipping is not expected at restaurants'). It does not, however, distinguish itself from clearly related siblings such as 'country_tipping', 'tipping_countries', or 'tipping_services', which an agent must resolve on its own.

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 example implies the intended use case (filtering by service-level tipping norms rather than by country name), but there is no explicit when-to-use/when-not-to-use statement or named alternative. With three plausible sibling tools covering tipping by country, the absence of routing guidance is a real gap.

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