Skip to main content
Glama

equibles

by io.github.daniel3303

Institution Sector Allocation

GetInstitutionSectorAllocation
Read-only

Get an institution's 13F portfolio allocation for a given report quarter (defaults to the latest), grouped by fine-grained industry (default) or rolled up by sector via groupBy. Returns a markdown table sorted by % of portfolio descending, with stocks lacking a classification collapsed into a single 'Unclassified' row at the end. Published values normally use report-date closing prices, may fall back to filer values, and can be zero when unavailable. Use SearchInstitutions for an exact CIK; ambiguous partial names return candidates instead of selecting silently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupByNoGrouping level: 'industry' (default, fine-grained) or 'sector' (broad rollup)industry
reportDateNoQuarter-end 13F report date in YYYY-MM-DD format (defaults to the holder's latest; an off-quarter date snaps to the nearest report on or before it)
institutionNameYesInstitution name or CIK (a unique partial resolves; ambiguous partials return candidate CIKs)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / institutionName / description
      Previous value: -"Institution name or CIK (partial names resolve to the largest recently-active 13F filer)"New value: +"Institution name or CIK (a unique partial resolves; ambiguous partials return candidate CIKs)"
  2. Changed1 schema field changed
    • changedInput schema / properties / institutionName / description
      Previous value: -"Institution name or CIK (partial names resolve to the largest 13F filer)"New value: +"Institution name or CIK (partial names resolve to the largest recently-active 13F filer)"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive behavior, and the description adds substantial behavioral context: outputs a markdown table, sorts by portfolio percentage, collapses unclassified stocks, falls back from report-date prices to filer values, and may return zeros. No contradiction with annotations.

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?

Four information-dense sentences, each earning its place. The core purpose is front-loaded, followed by output format, price-source caveats, and name-resolution guidance, with no filler or repetition.

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 fully covers return format, ordering, unclassified rows, and data caveats. It also covers defaults, grouping, date snapping, and name resolution, giving an agent everything needed to invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds valuable meaning beyond the schema: groupBy semantics, reportDate defaulting and off-quarter snapping, and how institutionName resolution handles unique vs ambiguous partials. This gives an agent operational guidance the schema alone does not provide.

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: 'Get an institution's 13F portfolio allocation' for a report quarter, with explicit grouping by industry or sector. It also distinguishes itself by describing the sorted markdown table output and unclassified-row behavior, which separates it from similar portfolio-related siblings.

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?

Provides clear context: defaults to latest report, supports fine-grained industry or sector rollup, and returns candidates for ambiguous partial names. It explicitly directs users to SearchInstitutions for exact CIK matching, but it does not contrast itself with closely related tools like GetInstitutionPortfolio or GetInstitutionConsensusHoldings.

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

All equibles toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources