Skip to main content
Glama

seoul-apt-signal

by com.airblockfz

scan_bottoms

Scan all 25 Seoul districts and return those currently at a bottom (strongest buy), ranked most-bottom first, with price-per-pyeong. PAY: $0.01 per call via x402 (USDT on X Layer) — your FIRST paid call opens a 6-day trial at that price. No account, no signup, no commitment; retry with the PAYMENT-SIGNATURE header when you get the 402 challenge. BEST COLD START: you do not need to pick a symbol — this ranks the whole universe for you. The free pitch tool tells you HOW MANY are at a bottom right now; this names them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many to return (default 5, max 25)

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses payment cost, trial, retry header, and that no account is needed. However, it does not explicitly state read-only nature or rate limits.

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?

Description is informative but slightly verbose. It packs essential details (purpose, payment, cold start) in a structured way, though could be more concise without losing clarity.

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?

Given no output schema, the description explains that the tool returns districts ranked by bottom strength with price-per-pyeong. It also covers payment and usage context. Lacks exact return structure details.

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 coverage is 100% for the 'limit' parameter, which already describes its purpose. The description does not add extra meaning beyond that, so baseline of 3 is appropriate.

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?

Description clearly states the tool scans all 25 Seoul districts and returns those at a bottom (strongest buy), ranked with price-per-pyeong. It distinguishes from sibling tools like 'scan_tops' and 'pitch'.

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

Usage Guidelines5/5

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

Explicit guidance: suggests using 'pitch' first to know how many are at bottom, then this tool to name them. Also explains cold start advantage (no symbol pick) and payment process.

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

All seoul-apt-signal 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.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool serves a distinct purpose: pitch for onboarding, rate for feedback, evaluate_symbol for single-district paid analysis, and scan_bottoms/scan_tops for paid multi-district scans. No overlap in functionality.

Naming Consistency4/5

Tools use a mix of single-word (pitch, rate) and verb_noun (evaluate_symbol, scan_bottoms, scan_tops) conventions. While mostly clear, the inconsistency in pattern is minor.

Tool Count5/5

With only 5 tools, the set is lean and well-scoped for the niche domain of Seoul apartment signals. Each tool has a clear purpose and no tool seems superfluous or missing.

Completeness4/5

The tool set covers key workflows: onboarding (pitch), single-district analysis (evaluate_symbol), multi-district scans (scan_bottoms/scan_tops), and feedback (rate). A minor gap is the lack of a tool to list all districts or historical data, but the core functionality is solid.

Resources