Skip to main content
Glama

Kolada Se

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.8/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it discloses data sources (SEC EDGAR/XBRL for companies, FAERS for drugs), fiscal year handling, sorting by primary metric, and citation URIs. No contradiction with annotations (readOnlyHint, etc.).

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?

The description is a single paragraph that efficiently packs all necessary information: trigger phrases, entity types, data sources, sorting, and value proposition. No redundant sentences.

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 the tool's complexity (two entity types, multiple data sources, no output schema), the description covers input semantics, data sources, sorting, and the benefit of replacing multiple lookups. It leaves little ambiguity for an AI agent.

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 parameter descriptions, but the description enriches semantics by specifying exact data pulled for each type (e.g., revenue, net income for companies; adverse-event counts for drugs) and providing example inputs (tickers, drug names).

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 that the tool performs side-by-side comparison of 2–5 companies or drugs in a single parallel call. It lists trigger phrases like 'Compare X and Y' and explicitly distinguishes from sequential single-entity lookups, making its purpose unmistakable.

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 recommends preferring this tool over sequential lookups when comparing entities. It explains behavior for each entity type (company vs drug). While it doesn't explicitly state when not to use, the context is clear enough for an agent to decide.

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

All Kolada Se 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.7/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (explicitly identical when no routing candidate is active), ask_pipeworx_grounded, deep_research, and validate_claim all answer factual questions through the same underlying router. The prediction-market cluster (polymarket_edges, polymarket_arbitrage, bet_research, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) has substantial purpose overlap that requires reading long descriptions to disambiguate.

Naming Consistency3/5

Mostly snake_case, and the pipeworx_/polymarket_/ask_ prefixes give some structure, but conventions are mixed: some tools are verb_noun (list_municipalities, get_data), some are bare verbs (forget, recall, remember), and some are noun phrases (entity_profile, deep_research, bet_research, recent_changes). The inconsistent prefixing across meta-tools (ask_, deep_, entity_, scan_, validate_) makes the surface feel less predictable than it could be.

Tool Count2/5

35 tools is on the heavy side, but the bigger problem is that the server name 'Kolada Se' matches only 4 tools (search_kpi, list_municipalities, list_org_units, get_data), while the other 31 tools belong to unrelated domains (Pipeworx data routing, prediction markets, memory, subscriptions, AI visibility). This is a severe scope mismatch that makes the count feel bloated and unfocused.

Completeness3/5

For the Kolada domain named by the server, the surface is minimal: you can search KPIs, list municipalities, list org units, and fetch single-KPI data, but there is no multi-year bulk fetch, cross-municipality comparison, or unit-level data retrieval. The broader Pipeworx/prediction-market surface is fairly feature-complete, but it is not what the server name implies, so the set as a whole leaves the apparent domain thinly covered.

Resources