Skip to main content
Glama

seoul-apt-signal

by com.airblockfz

evaluate_symbol

Return the bottom/top verdict for one Seoul district apartment market (25 districts). Accepts Korean (강남구, 강남) or romanized (Gangnam, Nowon, Mapo …) names. zone = strong_buy|buy|neutral|sell|strong_sell, score -100..+100 (bottom>0, top<0). Price = volume-weighted median per pyeong (KRW 10k) from official MOLIT closed transactions. Informational only. 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. The free pitch tool shows a live verdict for this market's showcase symbol only — this tool answers ANY symbol and adds the per-indicator breakdown behind the score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesDistrict, e.g. Gangnam, 강남구, Nowon

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided. Description discloses informational nature, payment requirement, retry mechanism on 402, trial offer, and addition of per-indicator breakdown. Transparent without contradictions.

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 somewhat long but well-structured with key details front-loaded. Every sentence adds value, though could be slightly more concise.

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?

Given simple tool with one parameter and no output schema, description fully explains inputs, outputs, usage, payment, and error handling. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% with example, but description adds value by specifying accepted formats (Korean, romanized) and listing examples like 'Gangnam, 강남구, Nowon', going beyond 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?

The description clearly states it returns a bottom/top verdict for one specific Seoul district, with details on output (zone, score, price). It distinguishes from siblings like 'pitch' (free but limited) and scan tools.

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?

Provides clear context: use for any district symbol, mentions free alternative 'pitch' for showcase, and describes payment model. Lacks explicit when-not-to-use but sufficient.

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