Skip to main content
Glama

Landprice

by io.github.pipeworx-io

Compare Entities

compare_entities
Read-onlyIdempotent

"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type: "company" or "drug".
valuesYesFor company: 2–5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2–5 names (e.g., ["ozempic","mounjaro"]).

TDQS

A4.7/5.0
Behavior4/5

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

Adds details beyond annotations: mentions pulling latest 10-K data with correct fiscal year handling for companies, and FAERS/FDA/trial data for drugs. Results sorted by primary metric. Returns URIs. No mention of rate limits or error cases, but annotations already cover safety and idempotency.

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 relatively long but well-structured, starting with trigger phrases and key instructions. Every sentence adds value, though could be slightly more concise without losing information.

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?

Covers trigger phrases, entity types, data sources, handling of fiscal years, sorting, return format including URIs. No output schema exists, but description adequately describes return values. Complete for a complex tool.

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 coverage is 100%. Description explains the 'type' enum values (company/drug) and what data they pull. For 'values', provides examples (tickers for company, drug names) and constraints (2-5 items). Adds significant meaning 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 the tool performs side-by-side comparison of 2-5 companies or drugs, with specific data sources and examples. It distinguishes itself from sibling tools like entity_profile by emphasizing parallel lookup over sequential lookups.

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?

Explicitly instructs 'ALWAYS PREFER over sequential single-pack lookups when comparing entities' and provides example query phrases. Also mentions it replaces 8-15 sequential lookups, offering clear when-to-use guidance.

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

All Landprice 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
Disambiguation2/5

Several tool clusters have unclear boundaries. `ask_pipeworx_beta` is explicitly described as currently identical to `ask_pipeworx`, `discover_tools` overlaps with `suggest_questions`, and the six Polymarket tools (`bet_research`, `polymarket_edges`, `polymarket_arbitrage`, etc.) blur together for opportunity-finding. An agent would struggle to pick the right tool without reading every description carefully.

Naming Consistency4/5

Naming is overwhelmingly consistent snake_case with a verb_noun or noun pattern (`ask_pipeworx`, `list_subscriptions`, `validate_claim`, `recent_changes`). The `polymarket_*` and `ask_pipeworx_*` families follow clear conventions. Minor deviations like `bet_research`, `entity_profile`, and `landprice_points` being noun-first are still readable and predictable.

Tool Count2/5

32 tools is heavy for a server named 'Landprice' when exactly one tool (`landprice_points`) actually concerns land prices. The vast majority of tools constitute an unrelated general-purpose data research and prediction-market platform, making the count feel bloated and scattershot relative to the server's stated purpose.

Completeness3/5

For the actual broad scope revealed by the tools — structured data lookup, grounded verification, deep research, entity resolution, comparison, monitoring, and memory — the surface is reasonably complete with no obvious dead ends. However, for the 'Landprice' domain implied by the server name, coverage is nearly absent: only Japan is covered, with no other countries, address search, or property-level data.

Resources