Skip to main content
Glama

Dadao Value

evaluate_company

Run Dadao Value's five-step business-owner checkup on a US-listed company (incl. ADRs). Returns a dual-axis conclusion (business quality tier x price tier), a deterministic EPSxPE fair-value range, the first two analysis steps, three must-answer questions, and sourced key figures (FMP + SEC EDGAR). Education/framework only: never a recommendation, price prediction, or buy/sell instruction. Free tier; steps 3-5 are locked (full report is a paid human checkout). Results are cached per company for 24h.

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": {
      "ticker": "<ticker>"
    },
    "name": "evaluate_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesUS ticker symbol (e.g. AAPL) or company name (e.g. Apple).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry behavioral context. It discloses the educational disclaimer, free-tier lock on steps 3-5, paid full report checkout, data sources (FMP + SEC EDGAR), and 24h caching, which is substantial. It omits auth and error behavior, so 4 rather than 5.

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 front-loaded and every clause supplies useful information: purpose, return values, disclaimer, tier limits, and caching. It is dense but not padded; a more structured presentation would improve scanability, so 4.

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?

With no output schema, the description must explain returns and limitations. It does so thoroughly: dual-axis conclusion, EPSxPE fair-value range, first two steps, must-answer questions, sourced figures, locked steps, and caching. Complete for an agent to decide and call.

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

Parameters3/5

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

Schema coverage is 100% for the single ticker parameter. The description reinforces scope ('US-listed company (incl. ADRs)') but adds no parsing, formatting, or ambiguity guidance beyond the schema, so the high-coverage baseline of 3 applies.

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?

The description uses a specific verb and resource ('Run ... checkup on a US-listed company') and enumerates the returned artifacts, so the tool’s function is unambiguous. It does not explicitly contrast with the sibling ask_framework, so it stops short of a 5.

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?

It states the applicable scope (US-listed companies, including ADRs) and the educational-only limitation, which implies when to use it. It does not name an alternative or specify when not to use it, leaving routing to the agent.

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