Skip to main content
Glama

Singstat Sg

by io.github.pipeworx-io

Search Tables

search_tables
Read-onlyIdempotent

Search Singapore official statistics tables (Department of Statistics Singapore) by keyword. Returns resource ids and titles. The id of a result (e.g. "M810001") is the resourceId used by table_data and table_metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesSearch term, e.g. "population", "gdp", "cpi".
searchOptionNoWhere to match the keyword. "all" (default) searches everything, "title" only table titles, "variable" only variable names.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "keyword": "population"
+  },
+  {
+    "keyword": "gdp",
+    "searchOption": "title"
+  }
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds context beyond annotations: specifies search domain (SG stats), keyword-based search, and output format. Annotations already cover safety and idempotency, so description enhances behavioral understanding.

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?

Two concise sentences with no filler. Efficiently conveys core functionality and relationship to sibling tools.

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?

Simple tool with complete annotations and schema. Description explains output and ID usage. No need for more given low complexity.

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 coverage is 100% with descriptions for both parameters. Description provides examples but adds limited new meaning beyond schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it searches Singapore official statistics tables by keyword, returns resource ids and titles, and distinguishes from siblings by mentioning table_data and table_metadata.

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?

No explicit when-to-use or when-not-to-use for alternatives, but implies use to get resource IDs for table_data and table_metadata. Lacks guidance on when to prefer this over other search tools.

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

All Singstat Sg toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources