Skip to main content
Glama
Sign In

Corridome

by com.corridome
OverviewDiscussionsAdmin

List funds by type

list_funds
Read-onlyIdempotent

Funds of one Form ADV type, A to Z, fifty at a time, each with its adviser and gross assets.

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": {
      "type": "<type>"
    },
    "name": "list_funds"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe fund type: private-equity, venture-capital, hedge, real-estate, securitized-asset, liquidity or other.
afterNoFor the next page: the previous page's next_after (or the last name it listed).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / after / description
      Previous value: -"Start after this name (A to Z), for the next page: the last name of the previous page."New value: +"For the next page: the previous page's next_after (or the last name it listed)."
    • changedInput schema / properties / after / maxLength
      Previous value: -200New value: +300
  2. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new facts: fixed page size of 50, alphabetical ordering, and that each row carries its adviser and gross assets. It does not say what happens at the end of the list or whether the cursor is name-based, so the addition is real but partial.

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 sentence, zero filler, with scope and ordering front-loaded. Nothing in it is redundant.

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 two-parameter read tool with no output schema, the description covers what comes back at a summary level (adviser, gross assets) and how paging works. It stops short of stating the exact row fields or termination condition, which an agent paging through results would want.

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 description coverage is 100% and both parameters are documented there, including the enum values and the 'next_after or last listed name' cursor semantics. The description's 'A to Z, fifty at a time' corroborates the ordering and page size behind the cursor but adds no syntax the schema lacks, so the baseline 3 applies.

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 sentence names the resource (funds), the scoping dimension (Form ADV type), the ordering (A to Z), the page size (fifty), and the payload (adviser and gross assets). That is enough to separate it from get_fund (single fund) and the search_* siblings, though it never names an alternative explicitly.

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 implied rather than stated: browsing one fund type at a time, paged. There is no explicit when-to-use, no exclusion such as 'use search_firms for cross-type queries', and no note that the type parameter is mandatory.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Corridome toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources