Skip to main content
Glama

An impersonal brief on one filed move, for an agent to act on

mirror_brief
Read-only

The same move as /verdict, flattened into a brief: what the investor did, when, at what price, against our value band, plus the verdict sentence. It carries NO quantity and NO instruction — sizing reads "not provided; the reader decides". It describes a public filing and a published value range; it is not advice and not a prediction. (GET https://app.deepvalues.ai/api/v1/mirror-brief/{ticker}, e.g. https://app.deepvalues.ai/api/v1/mirror-brief/AAPL?guru=warren-buffett — 0.01 credits per call; works with no credentials up to 5 call(s)/day per address) Missing data? Call request_data.

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>",
      "guru": "<guru>"
    },
    "name": "mirror_brief"
  }
}

Input Schema

NameRequiredDescriptionDefault
guruYes
tickerYesThe real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}.
quarterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / guru / examples
      Added value: +[
      +  "warren-buffett"
      +]
    • addedInput schema / properties / ticker / description
      Added value: +"The real ticker symbol, e.g. AAPL; share classes as BRK.B or BRK-B. Substitute it into the path (/fundamentals/AAPL), never the literal {ticker}."
    • addedInput schema / properties / ticker / examples
      Added value: +[
      +  "OXY"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say readOnly and openWorld; the description adds real behavioral context beyond that: no quantity, no instruction, `sizing` literally reads 'not provided; the reader decides', plus credit cost (0.01/call) and a 5 call/day unauthenticated ceiling. It stops short of describing pagination or response shape, but for a read-only single-fetch tool the disclosure is strong.

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?

Front-loads the payload definition and the negative claims before the transport details, and no sentence is pure filler. The parenthetical URL/credits/auth block is dense but each element is actionable.

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?

No output schema exists, and the description compensates by naming the fields the brief carries and, unusually, the one field it deliberately omits. Cost, auth, rate limit and a missing-data escape hatch are all present; only `quarter` semantics and return-format details are absent.

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 only 33%, so the description has to carry weight; it shows the guru query-param usage and ticker path substitution via a worked URL, which adds meaning for two of three params. The `quarter` parameter is never mentioned in either the schema or the description, leaving a real gap.

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 specific resource ('the same move as /verdict, flattened into a brief') and enumerates its payload: what the investor did, when, at what price, against the value band, plus the verdict sentence. It explicitly distinguishes itself from the sibling /verdict by describing the flattened relationship.

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?

Implies the choice between this and /verdict (use the brief when you want the flattened version) and gives an explicit fallback: 'Missing data? Call `request_data`.' It also gives the exact call form and the unauthenticated limit, but never states a when-not condition or when to prefer the full verdict.

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