Skip to main content
Glama

Realestateapi

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"]).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds significant context: for companies it pulls latest 10-K data (revenue, net income, cash, debt) from EDGAR/XBRL with correct fiscal year handling; for drugs it pulls FAERS counts, FDA approvals, and trial counts. It also notes sorted results and citation URIs. Lacks details on rate limits or error handling.

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?

The description is a single dense paragraph that front-loads example queries and key guidance. Every sentence adds value, but it could be slightly more structured with bullet points. However, it remains efficient and actionable.

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 adequately covers return value components (paired data, sorted by primary metric, citation URIs). It explains data sources for both entity types. It does not specify exact response format or pagination, but provides enough for an agent to understand what to expect.

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% with descriptions, but the description adds substantial meaning: it explains that 'values' can be tickers/CIKs for companies or drug names, and specifies the data sources (SEC EDGAR for companies, FAERS/FDA for drugs). This goes well beyond the schema's enum and array constraints.

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 comparisons of 2-5 companies or drugs, using specific verbs and resource types. It distinguishes from sibling tools like entity_profile by emphasizing parallel vs. sequential lookups. Example queries like 'compare X and Y' provide immediate clarity.

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 explicitly says 'ALWAYS PREFER over sequential single-pack lookups when comparing entities', providing strong usage guidance. It lists example user intents. However, it does not specify when NOT to use the tool or list alternatives for other use cases.

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

All Realestateapi 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.6/5.0
Disambiguation2/5

Multiple tools have overlapping research/lookup purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded and validate_claim both verify claims against sources, and six polymarket_* tools overlap on edge/arbitrage detection. The three realestateapi_* tools are distinct but sit awkwardly beside 31 unrelated tools.

Naming Consistency2/5

Naming conventions are mixed: snake_case prefixed tools (realestateapi_property_search), domain-prefixed tools (polymarket_edges), verb-noun tools (ask_pipeworx, compare_entities), noun phrases (entity_profile, recent_changes), and bare verbs (remember, forget, recall). There is no consistent verb_noun pattern across the set.

Tool Count2/5

34 tools is heavy, and the vast majority belong to the Pipeworx platform rather than the Realestateapi identity — only 3 of 34 tools are real-estate specific. The count is not well-scoped for the server's stated purpose.

Completeness2/5

For a real estate API the surface is severely thin: search, detail, and skip-trace only, with no market trends, tax history, rental estimates, or comparable-sales data. For the Pipeworx meta-domain the coverage is broader, but the server presents as Realestateapi, making the domain coverage a mismatch.

Resources