Skip to main content
Glama

The verdict line for one filed move

verdict
Read-only

One guru's disclosed move in one ticker, with the sentence Deep Values publishes about it and every number behind it: the company's legal name beside the ticker (name, null where we hold none), the three dates (traded by, filed, seen), the quarter-end close, the current price, and the intrinsic value band. value is the callable band (the blend ±25%) and is null whenever the verdict is not a call; estimates always carries what the valuation methods actually said, their lowest and highest central estimate, so a reader told we cannot call it can see why. One of six deterministic states — below_value, inside_band, above_value, ran_ahead, too_uncertain, no_value — computed the same way for every caller. The band is Deep Values' blended intrinsic value plus or minus 25%, and too_uncertain ("Our estimates disagree too much to call this one.") replaces the three band states when the methods' own central estimates are more than 3x apart, or one of them is not positive: the blend still exists and is still returned in value, but it is not a range anyone should be told a price sits inside. It is distinct from no_value, which means no valuation was computed at all. (GET https://app.deepvalues.ai/api/v1/verdict/{ticker} — 0.005 credits per call; works with no credentials up to 25 call(s)/day per address)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
guruYes
tickerYes
quarterNoQuarter end; default = the most recent quarter we hold.

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?

Annotations only declare readOnly/openWorld, so the description carries most behavioral burden and does add real context: the six deterministic states, the too_uncertain threshold (>3x spread or non-positive central estimate), the null value for non-call verdicts, and the rate limiting note (25 calls/day without credentials, 0.005 credits). It omits authentication requirements for higher volumes and error behavior, but supplies substantially more than annotations.

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?

Front-loads a rich purpose sentence, but then delivers dense explanatory prose including parentheses, embedded quotes of state semantics, and an endpoint/pricing parenthetical. Much of it is on-topic, yet a full-fledged parenthetical may not be needed for callable tool selection.

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 3-param read-only tool with no output schema, the description covers the returned shape (name, three dates, quarter-end close, current price, intrinsic value band, value, estimates, six states) so an agent can predict output structure and semantics without an output schema. Missing only explicit auth/error/edge-case details.

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 description coverage is only 33% and only the quarter parameter is documented (defaulting to most recent). The description does not explain guru (presumably a guru identifier/key) or ticker format, so it misses compensating for the coverage gap beyond what the schema already states.

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

Purpose5/5

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

States a precise verb+resource: returns one guru's disclosed move in one ticker, enriched with Deep Values' published sentence and all supporting numbers. Easily distinguished from siblings like guru_moves (list) or intrinsic_value (pure valuation).

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?

Implicitly scoped to a specific guru-ticker-quarter combination, but no explicit 'use this when' guidance or routing away from alternatives such as filings, intrinsic_value, or guru_moves. An agent could infer, but not confidently.

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