Skip to main content
Glama
Sign In

TeamedUp Intelligence — China & APAC Salary Data

by io.github.bp46
OverviewDiscussionsAdmin

list_cities

List all genuine metropolitan and prefecture cities available in the dataset. Accepts an optional "region" argument ("mainland", "greater", "intl"). Use before querying market data to ensure accurate city name matching.

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": "list_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoRegion scope: "mainland" (Mainland China), "greater" (Mainland + HK + TW), or "intl" (All APAC). Defaults to "mainland".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. 'List' implies a safe read, but the description never states that explicitly, nor does it say whether the result set is static reference data, how large it is, or whether it is paginated. For a simple read-only lookup tool these gaps are forgivable, but nothing beyond the obvious is disclosed.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action, then the parameter, then the usage cue. Efficient and readable; the only waste is restating enum values that the schema already documents completely.

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?

The tool is simple (one optional enum parameter, no nested objects) and the description covers action, scope, and sequencing adequately. However, with no output schema, the description never says what a returned 'city' looks like (name only, codes, region tags), which matters for an agent that must match names downstream. It also omits the 'all' enum value present in the schema.

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% and the enum meanings are already spelled out in the schema, so the description adds little. Worse, the description quotes only three values ('mainland', 'greater', 'intl') while the schema also allows 'all', which could lead an agent to believe 'all' is invalid or to confuse 'greater' with 'all'.

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?

States a specific verb and resource ('List all genuine metropolitan and prefecture cities') and scopes it to what is 'available in the dataset', which is enough for an agent to distinguish it from list_roles and list_taxonomies by noun alone. The vague qualifier 'genuine' slightly muddies what is actually returned, but the core action is unambiguous.

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?

Gives an explicit call-ordering instruction: 'Use before querying market data to ensure accurate city name matching', which tells the agent exactly where this tool fits in a workflow. It does not say when the tool is unnecessary (e.g. when a city name is already known to be valid), so there is no exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TeamedUp Intelligence — China & APAC Salary Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources