Skip to main content
Glama

Singapore Procurement

by io.github.pipeworx-io
OverviewAdmin

Singapore Search Awards

singapore_search_awards
Read-onlyIdempotent

Search Singapore government procurement tender awards from the official GeBIZ dataset on data.gov.sg (keyless). Full-text search over awarding agency, supplier name, and tender description. Returns each award with tender number, agency, supplier, description, awarded amount (SGD), award date, and status. Use for questions like "which company won contract X", "how much did agency Y award for Z", or listing recent government contract awards. Omit "query" to page through all awards. Amounts are in Singapore Dollars (SGD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax awards to return (1–100). Default 20.
queryNoOptional full-text keyword — matched across agency, supplier name, and tender description (e.g. "cloud", "Accenture", "Ministry of Health"). Omit to list all awards.
offsetNoNumber of matching awards to skip, for paging. Default 0.

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: +[
+  {
+    "limit": 20,
+    "query": "cloud"
+  },
+  {
+    "limit": 10,
+    "offset": 0,
+    "query": "Accenture"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds value by noting the keyless dataset source, full-text search fields, returned fields, and that amounts are in SGD. No contradictions.

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?

Five sentences, each earning its place: purpose, scope, search fields, return fields, usage examples, paging hint, currency. Front-loaded with the primary action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search-only tool with 3 optional params and no output schema, the description covers all relevant details: input behavior, output fields, and usage examples. No critical gaps.

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?

Input schema has 100% coverage with descriptions for all 3 params. The description adds context beyond the schema: clarifies full-text fields ('awarding agency, supplier name, and tender description'), explains behavior when query is omitted, and specifies currency.

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?

The description clearly states the tool searches Singapore government procurement tender awards from the official GeBIZ dataset. It specifies the verb 'search' and the resource 'tender awards', and distinguishes it from siblings by naming the dataset and scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage examples ('which company won contract X') and a hint to omit 'query' to page through all awards. However, it does not explicitly state when not to use this tool versus alternatives, though the sibling list contains no similar tools.

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

All Singapore Procurement 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