Skip to main content
Glama

Buffett Indicator with zone classification

indicators_buffett
Read-only

US corporate equities ÷ GDP, with zones (significantly undervalued through significantly overvalued) and historical percentile. (GET https://app.deepvalues.ai/api/v1/indicators/buffett — 0.001 credits per call ($0.005 when paid per call over x402); works with no credentials up to 25 call(s)/day per address) Missing data? Call request_data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "indicators_buffett"
  }
}

Input Schema

NameRequiredDescriptionDefault
history_yearsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations: cost per call, a free tier of 25 calls/day per address, and an explicit fallback to request_data when data is missing. It does not describe the shape of the returned zone/percentile data, but with readOnlyHint and openWorldHint already supplied, the operational details are the more valuable addition.

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 definition is compact and front-loads the metric definition before operational details and the fallback. The pricing and URL are dense but useful for an agent deciding whether and how to call it; little wording is wasted.

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?

For a single-parameter read-only indicator tool with no output schema, the description adequately explains the metric and the available zone/percentile outputs. The main completeness gap is the unexplained history_years parameter, which affects how much history underlies the returned percentile.

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?

The sole parameter, history_years, is never mentioned in the description, and the schema supplies only a type, default, and maximum with no semantic description. The description therefore does not compensate for the 0% schema description coverage or explain how the history window affects the percentile and zone calculations.

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 names the exact metric (US corporate equities ÷ GDP) and the returned features (zone classification and historical percentile), making the tool's purpose immediately clear. It does not explicitly differentiate itself from the sibling indicator tool indicators_shiller_pe, but the metric itself is distinctive.

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 gives operational context for calling without credentials and a fallback ('Missing data? Call request_data'), which is useful usage guidance. However, there is no explicit guidance on when to choose this indicator versus related indicator tools such as indicators_shiller_pe.

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