Skip to main content
Glama

Dadao Value

ask_framework

Ask a value-investing framework question answered from the Dadao Value knowledge base (127 rules, 141 historical teaching cases): what makes a good business, moats, pricing power, valuation discipline, position discipline. Education only; stock picks and price predictions are declined.

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": {
      "question": "<question>"
    },
    "name": "ask_framework"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe framework question, in Chinese or English (max 500 chars).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 burden. It usefully discloses scope of the corpus (127 rules, 141 cases) and refusal behavior for stock picks/price predictions, but says nothing about response shape (e.g., whether answers cite rules or cases) or any latency/rate constraints. Good on policy, thin on output behavior.

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?

One compact sentence with a parenthetical, purpose front-loaded before the topic list and the refusal clause. Dense but every clause carries information; no filler.

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?

For a low-complexity single-parameter query tool with no output schema, the definition covers purpose, domain scope, and refusal policy adequately. The remaining gap is what a returned answer looks like and whether follow-up context is retained, which is minor here.

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?

Single parameter with 100% schema description coverage, including the 500-character limit and bilingual Chinese/English input. The description adds no meaning beyond the schema on how to phrase a question, so the schema-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?

States a specific verb and resource ('Ask a value-investing framework question') backed by a named knowledge base, and enumerates the covered topic areas (moats, pricing power, valuation, position discipline). It does not explicitly contrast with the sibling evaluate_company, so the boundary between 'ask about the framework' and 'evaluate a company' is left for the agent to infer from the topic list.

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?

Gives a clear usage envelope: framework/educational questions in, with an explicit exclusion ('stock picks and price predictions are declined'). That tells the agent both when to use it and when a request will be refused, though it never names an alternative tool for company-specific evaluation.

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