Skip to main content
Glama
Sign In

autario-mcp

by io.github.Autario
OverviewDiscussionsAdmin

list_investors

Read-onlyIdempotent

List the well-known investors whose SEC Form 13F portfolios autario tracks (Berkshire Hathaway, Bridgewater, Pershing Square, Scion, Renaissance, ARK and more), with the latest reported quarter end, total reported value, number of positions and largest holding. Use it to find the slug get_investor_portfolio takes. Form 13F is filed up to 45 days after the quarter ends, so positions are as of the quarter end, not today.

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

Input Schema

NameRequiredDescriptionDefault
formatNoOutput wire format for this MCP call. Default 'toon' (Token-Oriented Notation, fewest tokens, best for tabular rows). 'compact' = minified JSON. 'json' = pretty JSON for readability. The REST API always returns JSON regardless.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world scope, so the safety profile is covered; the description adds what the annotations cannot: the data-freshness model (13F filed up to 45 days after quarter end, positions as of quarter end, not today). It also enumerates the return fields (latest reported quarter end, total reported value, number of positions, largest holding), which matters since no output schema exists.

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?

Three sentences: what it lists and returns, how it is used relative to a sibling, then a caveat about data currency. The purpose is front-loaded and every clause carries information the agent would otherwise have to guess.

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 single-optional-param list tool with no output schema, the description supplies both the returned field set and the temporal caveat that determines whether the numbers are current. Nothing needed to call it correctly or interpret results 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 description coverage is 100% and the single `format` enum is fully documented in the schema, so the schema carries the burden. The description says nothing about the format parameter, so it adds no meaning beyond the structured field; baseline 3 applies.

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?

States a specific verb and resource ("List the well-known investors whose SEC Form 13F portfolios autario tracks") and enumerates concrete examples (Berkshire Hathaway, Bridgewater, Pershing Square...), so an agent knows exactly what domain this covers. It also names the sibling it feeds into, distinguishing it from get_investor_portfolio.

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?

"Use it to find the slug get_investor_portfolio takes" gives an explicit routing rule to the alternative tool and the condition that selects it. No exclusion cases are stated, but the single named alternative and the discovery-then-fetch workflow leave little to infer.

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

All autario-mcp 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