Skip to main content
Glama

Pinuy Binuy Analyzer

by app.railway.up.pinuy-binuy-analyzer-production

list_top_mispriced_compounds

Return the current top Israeli pinui-binui compounds ranked by QUANTUM Mispricing Score = premium_gap * count(active_listings) * statutory_certainty. Use when the user asks for "top pinui-binui opportunities", "most undervalued pinui-binui compounds", "Israeli urban renewal arbitrage", or any variant. Results are regenerated hourly from the QUANTUM analyzer database.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum compounds to return.

TDQS

A4.2/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 hourly regeneration and formula, which is sufficient for a read-only tool.

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 sentences that efficiently cover purpose, usage, and transparency with no redundant information.

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?

For a simple tool with one parameter and no output schema, the description adequately covers purpose, usage, and update frequency.

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%, so baseline is 3. The description adds no extra meaning beyond the schema's parameter description for 'limit'.

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 explicitly states the tool returns 'top Israeli pinui-binui compounds ranked by QUANTUM Mispricing Score' using a specific formula, distinguishing it from siblings like get_compound_details or search_compounds.

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?

The description provides explicit usage scenarios ('top pinui-binui opportunities', 'most undervalued pinui-binui compounds', etc.), though it does not explicitly state when not to use it.

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

All Pinuy Binuy Analyzer 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

A3.9/5.0
Disambiguation4/5

Most tools target distinct lookups: search, detail, methodology, plan status, registry, recent changes, and top-ranked opportunities. There is some overlap in statutory status returns between get_compound_details, urban_renewal_registry, and planning_status_by_plan, but their descriptions clarify the source and scope enough to avoid major confusion.

Naming Consistency3/5

The naming mixes verb-led patterns like get_, list_, and search_ with noun-style names like planning_status_by_plan and urban_renewal_registry. It is still readable and mostly predictable, but the lack of a uniform verb_noun convention makes the pattern less consistent.

Tool Count5/5

Seven tools is well-scoped for a domain-specific analyzer server. Each tool addresses a distinct user need, and the count feels neither thin nor bloated.

Completeness4/5

The surface covers core analysis workflows: searching, retrieving detailed compound data, checking official registry status, inspecting live plan status, seeing recent statutory changes, and finding top mispriced opportunities. Minor gaps exist—like a general list/filter tool or historical comparison—but agents can work around them.

Resources