Skip to main content
Glama
edgar13f-mcp

edgar13f-mcp

by Serios16

find_manager

Find a manager's CIK by name, prioritizing entities with Form 13F filings, so you can resolve the manager before querying holdings or filings.

Instructions

Find a manager's CIK from its name (a case-insensitive substring of current or former EDGAR entity names). Candidates that have filed Form 13F come first. Use it before the other tools when you only know the name. entity_name is EDGAR's current name (not point-in-time); with as_of, has_13f_filings counts only 13F filings dated on or before as_of.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
as_ofNoISO-8601 knowledge date: the answer uses only what was publicly filed on EDGAR by this date.
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and mostly succeeds: it discloses case-insensitive substring matching over current or former EDGAR names, ranking of candidates with 13F filings first, and the point-in-time caveat for as_of. It does not explain limit behavior or the exact return structure, but the core lookup semantics are unusually well described.

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 compact and front-loaded, with no filler. It is dense and slightly awkward around entity_name, but every sentence contributes useful behavioral or parameter information.

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 three-parameter lookup tool with no annotations and no output schema, the description covers the essential matching, ranking, and as_of semantics well enough to invoke it correctly. The main missing piece is limit behavior and any hint about the returned candidate fields, which keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description adds important meaning beyond the schema. It explains that name is a case-insensitive substring of EDGAR entity names and clarifies the as_of effect on has_13f_filings, but it does not explain the limit parameter's role in candidate selection.

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: find a manager's CIK from its name. It also explains EDGAR name matching and ranking, which clearly distinguishes this lookup from the sibling holdings and filings tools.

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 when-to-use guidance: use this before the other tools when you only know the name. It does not explicitly name the alternatives or state when not to use it, but the condition for use is strong and actionable.

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