Skip to main content
Glama

analyze singapore condo

analyze_singapore_condo
Read-only

Analyze Singapore private residential property (condos, apartments, ECs): price trends, rental yields, project and district comparisons, using ChatProperty on Finch. Returns the agent's official description, price, free runs, a run link and a ready-to-send request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_singapore_condo"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoOptional short description of what the user wants. Do not include private documents or secrets.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the read-only and open-world profile, and the description adds meaningful behavioral detail beyond them: it discloses that the response contains the agent's description, price, free runs, a run link, and a ready-to-send request. That hints the tool prepares rather than executes the analysis, which is valuable; the exact execution flow (must the agent send the request via another tool?) is left slightly ambiguous.

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?

Two sentences, front-loaded with the domain and capabilities, then the return payload. Dense but every clause carries information; the parenthetical (condos, apartments, ECs) could arguably be folded into the schema, but it clarifies scope cheaply.

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?

No output schema exists, and the description does explain the return contents (agent description, price, free runs, run link, ready-to-send request), which is the main thing an agent needs. For a one-optional-param, low-complexity routing tool this is nearly sufficient, with only the follow-up invocation step and any cost/auth implications unaddressed.

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?

There is a single optional `task` parameter whose schema description has 100% coverage, so per the baseline this is a 3. The description says nothing additional about how to phrase `task` or what it influences in the output, so it adds no meaning beyond the schema.

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?

Names a specific verb (analyze) and a precise resource domain (Singapore private residential property, incl. condos/apartments/ECs) and enumerates the analyses offered: price trends, rental yields, project and district comparisons. The domain scope alone separates it from every sibling (e.g., analyze_hyperliquid_us_stock_perp, assess_onchain_business).

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?

Usage is only implied by the domain name — an agent can infer this applies to Singapore condo questions, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as search_finch_agents / get_finch_agent for other domains. No prerequisites (e.g., that this prepares a Finch run rather than executing it end to end) are stated.

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.