Skip to main content
Glama

One guru: bio + top holdings

guru
Read-only

One guru: bio + top holdings (GET https://app.deepvalues.ai/api/v1/gurus/{slug}, e.g. https://app.deepvalues.ai/api/v1/gurus/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": {
      "slug": "<slug>"
    },
    "name": "guru"
  }
}

Input Schema

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

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.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint; the description adds material context beyond them — per-call credit cost, an unauthenticated rate cap, and a fallback path via request_data. It does not describe response shape or pagination, but the key operational constraints are disclosed.

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-loaded: capability first, then endpoint, cost and quota, then the escape hatch. The parenthetical is dense but every element (URL template, cost, quota) is operationally relevant, with little wasted text.

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 single-parameter read tool with no output schema, the definition covers purpose, endpoint, cost, auth limits, and failure handling. The lack of any note on the response contents is a minor gap given how simple the call is.

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?

With 100% schema description coverage and a single required slug parameter, the schema already carries the semantics. The description reinforces the slug with a full URL example and notes where slugs come from (GET /gurus), which is marginally useful but well within what the schema and sibling gurus already imply.

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 specific resource (a single guru) and its payload (bio + top holdings), which clearly differentiates it from the listed siblings such as gurus, guru_moves, guru_portfolio. It stops short of explicitly naming which sibling to use for portfolio breakdowns, so it is clear but not fully sibling-routing.

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?

It gives the calling context (one guru by slug), states the cost (0.01 credits per call), the credential-free quota (5 calls/day per address), and routes the agent to request_data when data is missing. There is no explicit when-not-to-use versus guru_portfolio or smart_money_holdings, but the practical guidance is solid.

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