Skip to main content
Glama

Air Quality Psi

air_quality_psi
Read-onlyIdempotent

Current Pollutant Standards Index (PSI) from Singapore's National Environment Agency, by Singapore region (north, south, east, west, central).

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": {},
    "name": "air_quality_psi"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {}
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Current Pollutant Standards Index readings by region",
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds meaningful context beyond them: the data publisher (NEA), freshness ('Current'), and the regional breakdown the response is organized by. It does not state update cadence or rate limits, which keeps it from a 5.

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?

One sentence, front-loaded with the metric and source, followed by the granularity qualifier. Every clause earns its place and nothing is redundant.

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?

With an output schema present and no input parameters, the description need not explain return values or arguments; it covers source, metric and regional scope. Minor gaps remain around data freshness cadence and whether readings are hourly or averaged, but nothing blocks a correct call.

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 the schema carries no semantics to add to and the baseline for an empty parameter set is 4. The enumeration of regions in the description usefully documents the implicit dimension along which results vary.

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 names the exact metric (Pollutant Standards Index), the authoritative source (Singapore's NEA), and the granularity (five named Singapore regions). It is clearly separable from the sibling air_quality_pm25 by pollutant, though it never explicitly contrasts itself with that sibling.

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 only implied: 'Current' signals a real-time snapshot with no historical or ranged queries, and the region list signals the axis of interest. There is no explicit statement of when to prefer this over air_quality_pm25 or other air/weather siblings.

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.