Skip to main content
Glama

One guru's full portfolio at a quarter

guru_portfolio
Read-only

One guru's full portfolio at a quarter (GET https://app.deepvalues.ai/api/v1/gurus/{slug}/portfolio, e.g. https://app.deepvalues.ai/api/v1/gurus/warren-buffett/portfolio — 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": {
      "slug": "<slug>"
    },
    "name": "guru_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesGuru slug from GET /gurus, e.g. warren-buffett.
as_ofNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"Guru slug from GET /gurus, e.g. warren-buffett."
    • addedInput schema / properties / slug / examples
      Added value: +[
      +  "warren-buffett"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld; the description adds real behavioral context — per-call credit cost, an unauthenticated daily call cap, and the exact endpoint. It stops short of saying what authenticated access unlocks or what the payload contains.

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

Conciseness5/5

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

One dense parenthetical that front-loads the purpose, then endpoint, cost, limits, and fallback. No filler sentences; every clause carries information an agent needs.

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 two parameters and no output schema, the description should convey what a 'portfolio' payload is (holdings, weights, values) and how as_of behaves. Neither is addressed, leaving the agent to call somewhat blind on the return shape.

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 50%: slug is documented in the schema and echoed by the example URL, but as_of has no schema description. 'At a quarter' hints that as_of selects a reporting period, yet the date semantics (quarter-end only? any date?) are never clarified.

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 resource and scope: one guru's full portfolio as of a quarter, with the backing endpoint shown. It is clearly narrower than siblings like guru_moves or smart_money_holdings, though it never explicitly contrasts itself with them.

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?

Gives practical call conditions (0.01 credits per call, 5 calls/day unauthenticated) and a fallback ('Missing data? Call request_data'). It does not say when to prefer this over guru_moves or smart_money_holdings, so the routing guidance is only partial.

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