Skip to main content
Glama

Shiller PE with historical percentile

indicators_shiller_pe
Read-only

Shiller PE with historical percentile (GET https://app.deepvalues.ai/api/v1/indicators/shiller-pe — 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_shiller_pe"
  }
}

Input Schema

NameRequiredDescriptionDefault
history_yearsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses cost (0.001 credits per call, $0.005 via x402), credential-free access up to 25 calls/day per address, and the fallback tool when data is missing. It does not say what happens when the rate limit is exceeded or what the response looks like, so it falls short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is one compact sentence with no filler, and the purpose is front-loaded. However, the long nested parenthetical piles endpoint URL, credit pricing, x402 pricing, rate limits, and a fallback pointer into a single clause, which makes it harder to scan than separated statements would be.

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?

With no output schema and a terse title, the description carries the burden of explaining the returned data, and it only restates the title plus operational details. For a simple one-parameter read tool that is minimally adequate, but an agent still cannot tell what fields come back or how history_years shapes them.

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 single parameter history_years has 0% schema description coverage and is never mentioned in the description. The default (5) and maximum (100) are left to the agent to interpret, and the description adds no meaning about how the window affects the percentile output.

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 a specific indicator (Shiller PE) and its derived output (historical percentile), which is enough for an agent to know what it fetches. It does not contrast with the sibling indicator tool (indicators_buffett) or explain what the percentile means, so it stops short of full sibling differentiation.

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?

There is an implicit usage context (fetch this valuation indicator) and the description includes one explicit routing rule: 'Missing data? Call `request_data`.' But it gives no guidance on when to prefer this over other indicator/valuation tools, and no exclusions.

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