Get free sample data - real (not synthetic) district and project stats for a small fixed set of examples, in the exact same shape as the paid tools. Use this to verify the data fits your use case before calling the paid tools, which cover the full catalogue of districts and projects.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations present, so description carries full burden. States data is real and same shape, but doesn't disclose additional behaviors like limits or caching. Adequate for simple tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. Front-loaded with key info and efficiently conveys purpose and usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists, so return values are covered. Description explains data type and purpose well. Lacks mention of sample size or limitations, but sufficient for given complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has zero parameters (100% coverage), so baseline 4 applies. Description does not discuss parameters, which is acceptable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states 'Get free sample data' with specific qualifiers: real (not synthetic), same shape as paid tools. Distinguishes from siblings by emphasizing 'free' and 'sample' nature.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs to use this before paid tools to verify fit, implying paid tools for full catalogue. Clear context but lacks explicit when-not-to-use or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: data freshness, sample data, and listings for condos, HDB towns, and landed projects. No overlap.
All tool names follow a consistent verb_noun pattern (get_*, list_*) using snake_case, making them easy to understand.
Five tools is slightly on the smaller side but appropriate for a data portal's free tier; each tool serves a specific discovery or metadata function.
The tools cover discovery and metadata but lack any actual data retrieval endpoints (e.g., stats for districts or projects), which are described as paid. This leaves agents unable to complete core property data requests.