Skip to main content
Glama

Waqi Search Stations

waqi_search_stations
Read-onlyIdempotent

Search stations by keyword (city/region name). Returns station UID, name, current AQI, and location.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
keywordYesSearch keyword

Output Schema

NameRequiredDescriptionDefault
countYesNumber of matching stations
keywordYesSearch keyword used
stationsYesList of matching stations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the returned fields, which is useful, but does not mention ranking, result limits, error behavior, or search semantics beyond the keyword type.

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

Conciseness5/5

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

The description is two short sentences with the core action front-loaded and no unnecessary wording. It communicates the essential behavior and return shape efficiently.

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?

This is a simple one-parameter search tool with rich annotations and an output schema, so the description does not need to carry much weight. It covers the search input meaning and the return fields, leaving only minor gaps around result ordering and limits.

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?

Schema coverage is 100%, and the schema already defines the single required parameter. The description adds meaning by specifying that the keyword should be a city or region name, which is more informative than the schema's generic 'Search keyword' label.

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 states a specific verb and resource: search stations by keyword. It also clarifies that the keyword is a city or region name and lists the returned fields, which makes the tool's purpose clear. It does not explicitly differentiate itself from AQI lookup siblings, but the action and scope are still distinct.

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 by 'Search stations by keyword (city/region name)', which tells the agent how to query, but there is no explicit guidance on when this should be chosen over direct AQI lookup tools. No exclusions or alternative-selection criteria are provided.

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.