search_stationsSearch stations by keyword (city/region name). Returns station UID, name, current AQI, and location.
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | Yes | Search keyword |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of matching stations | |
| keyword | Yes | Search keyword used | |
| stations | Yes | List of matching stations |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "keyword": "shanghai"
+ },
+ {
+ "keyword": "los-angeles"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of matching stations",
+ "type": "number"
+ },
+ "keyword": {
+ "description": "Search keyword used",
+ "type": "string"
+ },
+ "stations": {
+ "description": "List of matching stations",
+ "items": {
+ "properties": {
+ "aqi": {
+ "description": "Current AQI value",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "country": {
+ "description": "Country where station is located",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "last_seen": {
+ "description": "Timestamp of last measurement",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "latitude": {
+ "description": "Station latitude",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "longitude": {
+ "description": "Station longitude",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Station name",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "station_id": {
+ "description": "Unique station identifier",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "timezone": {
+ "description": "Station timezone",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "url": {
+ "description": "Station information URL",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "keyword",
+ "count",
+ "stations"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by disclosing the return payload (station UID, name, current AQI, location), helping the agent anticipate what it will receive. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is front-loaded with the action, includes the key scope, and mentions the output fields. No wasted words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one required parameter, comprehensive annotations, and an output schema), the description is complete. It covers what the tool does, what it returns, and the parameter semantics. No significant gaps remain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema describes the keyword as 'Search keyword' with examples. The description enriches this by clarifying 'city/region name', which adds meaning beyond the schema. With 100% schema coverage, the baseline is 3, but this clarification bumps it to 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool searches stations by keyword (city/region name) and specifies the returned fields (UID, name, current AQI, location). This distinguishes it from sibling tools like get_aqi_by_city which likely return aggregated AQI rather than station-level metadata.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for finding stations when a city or region name is known. It provides clear context but does not explicitly state when not to use it or mention alternatives. Sibling tool names suggest there are more direct AQI retrieval tools, but no exclusion is mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.