Skip to main content
Glama

Curated guru roster

gurus
Read-only

60 hand-picked institutional investors — every name a serious value investor would recognize. Filter by style. (GET https://app.deepvalues.ai/api/v1/gurus — 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

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": "gurus"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
styleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds genuinely useful behavior beyond them: endpoint, cost of 0.01 credits per call, and unauthenticated access capped at 5 calls/day per address. It stops short of describing the response shape or what happens once the daily quota is exhausted.

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-loaded with the resource and tightly packed; the parenthetical pricing/quota block earns its place as operational detail. Slightly dense formatting with the URL-and-credits run-on, but no wasted sentences.

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?

For a simple read-only list with no output schema and two parameters, the description covers cost, quota, and a fallback path. It still omits the return format, pagination behavior around `limit`, and how this list relates to the per-guru tools, leaving a moderate gap.

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?

Schema description coverage is 0% for both parameters, so the description must carry the load. It gives meaning to the `style` filter but says nothing about `limit` (default 100, max 200) or about how strictly style values match, leaving a real gap for an undocumented parameter.

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 states a concrete resource and scope — a roster of 60 hand-picked institutional investors — and notes style filtering, so an agent knows it returns a curated list. However, it never distinguishes itself from the singular `guru`, `guru_moves`, or `guru_portfolio` siblings, so an agent must guess which roster-style tool fits.

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?

Usage is only implied: 'Filter by style' suggests the filtering use case, and the 'Missing data? Call `request_data`' line gives one explicit routing rule. There is no statement of when to prefer this over `guru` or `smart_money_holdings`, leaving the main selection decision to inference.

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