Skip to main content
Glama

List tracked funds

list_funds
Read-onlyIdempotent

Search and page through compact tracked 13F manager summaries. Use get_fund for positions and moves.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoOptional label, manager or CIK substring.
offsetNo

Output Schema

NameRequiredDescriptionDefault
fundsYes
totalYes
returnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / funds / items
      Added value: +{}
  2. First observed

TDQS

A4.3/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 openWorldHint, so the safety profile is covered. The description adds useful behavioral context by saying results are compact summaries and that results are paged, implying current results are not full position detail. It does not describe rate limits or auth needs, but those are not essential here.

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?

Two sentences are used with no wasted language. The primary purpose is front-loaded, and the sibling routing note follows immediately.

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?

The description covers purpose, scope, and the main alternative, while annotations cover safety and an output schema exists for return values. The only notable gap is that parameter behavior for limit and offset is left entirely to the schema, but otherwise the definition is sufficient for correct invocation.

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 only 33%, with limit and offset undocumented in the schema. The description's 'search and page through' weakly implies query and pagination parameters, but it does not explain limit/offset behavior, defaults, or constraints, so it fails to compensate for the coverage gap.

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: search and page through compact tracked 13F manager summaries. It also distinguishes the tool from get_fund, which is explicitly reserved for positions and moves. An agent can identify the intended operation without opening the 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?

The description gives a clear use case (searching and paging manager summaries) and names the primary alternative with its condition: use get_fund for positions and moves. This is explicit routing guidance rather than implied usage.

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.