Skip to main content
Glama

F1

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.9/5.0
Behavior5/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 valuable behavioral context: mentions specific data sources (SEC EDGAR/XBRL, FAERS), handles off-calendar fiscal years, returns sorted results and citation URIs. No 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?

The description is somewhat long but front-loaded with clear query examples. Every sentence adds value; however, it 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?

Given the tool has two well-defined parameters and no output schema, the description covers all necessary aspects: input format, data sources, behavior (sorted results, citation URIs), and entity-specific details. It is complete for an agent to select and invoke correctly.

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%, but description adds meaning beyond schema: explains that 'company' pulls latest 10-K data (revenue, net income, etc.) and 'drug' pulls FAERS counts. Provides examples for values parameter (e.g., tickers for company, 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 the tool does side-by-side comparison of 2-5 companies or drugs, specifying data sources (SEC EDGAR for companies, FAERS for drugs). It distinguishes itself from siblings like entity_profile by explicitly noting it replaces sequential single-entity 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?

The description provides explicit usage guidance: 'ALWAYS PREFER over sequential single-pack lookups when comparing entities.' It gives example query patterns ('X vs Y', 'which is bigger') and specifies entity types with clear data points.

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

All F1 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

Several tools are near-clones: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded differ mainly by mode, and deep_research overlaps with all of them. The five polymarket_* tools plus bet_research also blur together, and discover_tools vs suggest_questions both serve a 'what can I do' purpose.

Naming Consistency3/5

All names are readable snake_case, but the convention is mixed: verb-first (get_current_standings, validate_claim, scan_dependency), noun-first (polymarket_edges, pipeworx_trending), and bare verbs (remember, forget, subscribe). The F1 tools follow a clean get_* pattern that doesn't extend to the rest of the set.

Tool Count2/5

35 tools is excessive, especially since the server is named 'F1' but only 4 tools relate to F1. The set could be consolidated substantially: three ask_pipeworx variants, multiple overlapping polymarket scanners, and two tool-discovery helpers all add weight without clear scope.

Completeness2/5

The F1 side is thin: no qualifying results, constructor standings, lap data, circuits, or driver search by name. The Pipeworx half is broad, but it belongs to a different domain, leaving the overall surface feeling incomplete for either purpose.

Resources