Skip to main content
Glama

GetZeroslide Singapore company register

lookup_uen

Look up one Singapore company by its UEN (Unique Entity Number). Returns name, status, type, registration date, industry, address, officer count and former names from ACRA.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "uen": "<uen>"
    },
    "name": "lookup_uen"
  }
}

Input Schema

NameRequiredDescriptionDefault
uenYesUEN, e.g. 201912345K

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return fields and the ACRA source, and 'look up' implies a read-only operation, but it omits error behavior, permission requirements, rate limits, and what happens for unknown UENs.

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 tightly written sentences with no filler. The primary purpose is front-loaded, and the return-field detail follows efficiently.

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 no output schema, the description helpfully enumerates the returned fields (name, status, type, registration date, industry, address, officer count, former names) and names the data source. It is largely complete for a simple single-record lookup, though edge cases like not-found behavior remain unstated.

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 description coverage is 100% for the single parameter, which already documents the UEN format with an example. The description adds the acronym expansion '(Unique Entity Number)' but no additional syntax or validation detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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: 'Look up one Singapore company by its UEN'. The word 'one' and the UEN key distinguish it from bulk/search siblings like search_companies, though it does not name those alternatives explicitly.

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?

Implies usage when you already have a UEN and want a single company record, but provides no explicit when-to-use vs alternatives guidance and no exclusions. Sibling tools are never mentioned.

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.

Resources