Skip to main content
Glama
Hug0x0
by Hug0x0

singapore_query_businesses

Read-onlyIdempotent

Query ACRA-registered businesses and entities with exact filters, column text search, field selection, sorting, and pagination; inspect dataset fields before filtering to return accurate results.

Instructions

Query Entities Registered with ACRA (Accounting and Corporate Regulatory Authority). Topic: economy. Inspect dataset d_3f960c10fed6145404ca7b821f263b87 first for filter fields. Supports exact filters, column text search, fields, sort and pagination. Returns source coverage from the bundled catalog; fetch metadata for current coverage.

Input Schema

NameRequiredDescriptionDefault
qNoSearch text by column, e.g. {"school_name":"RAFFLES"}
sortNoe.g. month desc, resale_price desc; inspect fields first
limitNo
fieldsNo
offsetNo
filtersNoExact equality by field name, e.g. {"town":"ANG MO KIO"}

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
statusNo
sourcesYes
metadataNo
providerNo
warningsNo
served_atYes
error_codeNo
source_urlNo
dataset_urlNo
catalog_metadataNo
catalog_snapshot_atNo
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe read-only, idempotent, non-destructive operation. The description adds useful behavioral context by noting that returned source coverage comes from the bundled catalog and that metadata should be fetched for current coverage.

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?

The purpose is front-loaded and the text is efficient. The later sentences add operational guidance, though the metadata/coverage sentence could be slightly tighter.

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?

For a six-parameter query tool with nested q/filters objects and an output schema, the description covers purpose, prerequisite dataset inspection, supported query mechanics, and coverage caveats. The main remaining gap is sibling routing versus singapore_search_acra.

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?

The description names the main parameter families: exact filters, column text search, fields, sort and pagination. With only 50% schema description coverage, it partially compensates, but it does not add syntax or meaning beyond what the schema and parameter names already convey.

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: 'Query Entities Registered with ACRA'. The topic and dataset ID make the scope clear, but the description does not explicitly distinguish this tool from the sibling singapore_search_acra.

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?

It gives an important prerequisite: inspect dataset d_3f960c10fed6145404ca7b821f263b87 first for filter fields. However, it does not say when to use this tool instead of singapore_search_acra or singapore_query_dataset, so alternative selection is left implicit.

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

Deploy Server

Other Tools