Skip to main content
Glama

Rank funds by size

rank_funds
Read-onlyIdempotent

The largest private funds in the Corridome register, largest first, by the gross assets each reports on its adviser's Form ADV, of one fund type or of every type. Returns each fund's rank, name, type, gross assets, the filing's day and its adviser. Use it for the largest or biggest funds, with a type for the largest private equity, hedge or real estate funds; use list_funds for funds A to Z, and rank_firms for advisers.

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

Input Schema

NameRequiredDescriptionDefault
typeNoOnly funds of this type: private-equity, venture-capital, hedge, real-estate, securitized-asset, liquidity or other. Leave it out to rank every type together.
limitNoHow many funds to return, largest first, 1 to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds real value beyond that by naming the underlying data source (Form ADV gross assets) and enumerating the returned fields, which matters since no output schema exists. It stops short of noting truncation at the 50-fund maximum or whether missing gross-asset values are excluded.

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 ordering guarantee ('largest first') is front-loaded and the alternative routing is packed into a single closing clause with no filler. The prose is dense and clause-heavy, which slightly slows parsing, but every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-required-argument read tool with no output schema, the definition covers purpose, ranking basis, returned fields, and sibling routing. Nothing an agent needs in order to invoke it correctly is missing.

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 100%, and the schema already documents the enum values and that omitting type ranks all types together, so the description largely restates it. It adds only light interpretive framing, tying the type parameter to concrete use cases like largest private equity or hedge funds. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description states a specific verb (rank), a specific resource (private funds in the Corridome register), the ordering key (gross assets reported on Form ADV), and the scope (one fund type or all). It explicitly contrasts itself with list_funds (A-Z) and rank_firms (advisers), so an agent can pick the right tool without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a positive trigger ('Use it for the largest or biggest funds'), a refinement (pass a type for the largest PE, hedge or real estate funds), and names two alternatives with the conditions that select them. Both when-to-use and when-not-to-use are covered.

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