Skip to main content
Glama

falcon.sol comps

get_comps

falcon.sol: Trading comps table (market cap, EV, EV/Revenue, EV/EBITDA, P/E, P/FCF, margins, peer medians) for up to 12 tickers. Costs $0.05 USDC (x402).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tickers": "<tickers>"
    },
    "name": "get_comps"
  }
}

Input Schema

NameRequiredDescriptionDefault
pricesNo
tickersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose one critical trait: the tool costs $0.05 USDC via x402, which the schema does not reveal. However, it omits failure behavior, ticker format expectations (US vs. international, exchange suffixes), and what happens on partial data.

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 dense sentences, zero filler: the resource and its contents come first, then two hard constraints (ticker cap, price). Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Listing the returned fields partially compensates for the absent output schema, and the cost disclosure is essential. But the undocumented nested 'prices' parameter and the lack of any guidance on ticker format leave real gaps for a paid tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains the tickers parameter indirectly via 'up to 12 tickers' (matching maxItems=12), but the nested 'prices' object parameter is never mentioned—an agent cannot tell whether it is a per-ticker price override map or something else.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the specific resource (a trading comps table) and enumerates the exact metrics it contains, so an agent knows precisely what comes back. It doesn't explicitly contrast itself with siblings like get_financials or get_lbo, but 'comps table' is a distinguishable deliverable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the listed metrics (EV/Revenue, EV/EBITDA, P/E, peer medians) suggest peer benchmarking, and the 'up to 12 tickers' cap implies batching. There is no explicit when-to-use-this-vs-get_lbo-or-get_financials guidance and no stated preconditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources