Skip to main content
Glama

Rank advisers by size

rank_firms
Read-onlyIdempotent

The largest investment advisers in the Corridome register, largest first, by the gross assets their private funds report on Form ADV. Returns each adviser's rank, name, location, number of private funds, gross assets and the day its latest Form ADV was filed, with its corridome.com address. Use it for the largest or top advisers by assets, or to compare the biggest managers. It covers the hundred largest and ranks each adviser as it files: a group that files under several advisers appears once for each.

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_firms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many advisers to return, largest first, 1 to 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond annotations: the ranking basis, coverage of the hundred largest, returned fields, and the caveat that groups filing under several advisers appear once per adviser.

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 description is front-loaded with what the tool does and then adds return fields and usage guidance. It is mostly tight, though the usage sentence slightly repeats 'largest' and 'biggest' ideas.

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?

With no output schema, the description enumerates the returned fields and explains ranking basis, data source, coverage limits, and duplicate-adviser behavior. Combined with the fully documented single parameter and safety annotations, an agent has enough information to invoke it correctly.

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 single optional limit parameter is fully documented in the schema with default, minimum, and maximum. The description reinforces largest-first ordering but does not add parameter details beyond what the schema already provides.

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 and resource: ranking investment advisers by size, largest first, based on gross private-fund assets reported on Form ADV. It identifies the registry (Corridome) and distinguishes the tool from fund-ranking or firm-search siblings by focusing on advisers and asset rank.

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 clear usage context: use it for the largest or top advisers by assets, or to compare the biggest managers. It does not explicitly name alternatives or exclusions, so it falls short of full routing guidance, but the intended use case is unambiguous.

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