Skip to main content
Glama

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

Tipping levels explained

tipping_services
Read-onlyIdempotent

The services, tipping levels and methods the tipping tools use, explained, with counts. 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_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that results include counts, hinting at aggregate output, but says nothing further about structure or limits beyond what annotations provide.

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 reasonably tight, though the phrasing 'the tipping tools use, explained, with counts' is awkward and slightly confusing. The trailing promotional URL for other APIs does not help an agent invoke this tool and dilutes focus.

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 zero-parameter lookup tool with no output schema, the description should convey the shape of the returned data, and it only vaguely gestures at 'services, tipping levels and methods ... with counts'. It is adequate but leaves the agent guessing about the exact contents and whether it is a list or a keyed reference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The schema is closed and empty, consistent with a parameterless reference lookup.

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 indicates the tool returns reference information about services, tipping levels, and methods with counts, which conveys the general subject. However, it lacks a clear verb and framing (is it a list, a lookup table, a catalog?) and does nothing to distinguish it from siblings such as country_tipping, tipping_countries, or search_tipping_countries.

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?

There is no guidance on when to use this tool versus the closely named siblings country_tipping or tipping_countries, and no exclusions or prerequisites are stated. The agent must infer that this is a general reference endpoint from the phrase 'the tipping tools use' alone.

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