Skip to main content
Glama
SiftingIO

siftingio-mcp

Official

Company profile

stocks_profile
Read-only

Obtain a company profile compiled from SEC submission metadata by supplying a US equity ticker.

Instructions

Company profile assembled from SEC submissions metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesUS equity ticker, e.g. AAPL.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYes
cikYes
nameYes
exchangesNo
other_tickersNo
sic_codeNo4-digit SIC industry code.
sic_descriptionNo
entity_typeNo
fiscal_year_endNoFiscal year end, MMDD (e.g. 0930).
Behavior3/5

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

Annotations already declare readOnlyHint true and openWorldHint true, so the description adds the context of being assembled from SEC submissions metadata, but does not disclose additional behavioral traits like data freshness or potential missing data.

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 a single sentence, concise and front-loaded, but it could be slightly expanded to include when to use or what the output contains.

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 simple tool with one parameter and an output schema, the description adequately states the source and purpose. It could mention that it focuses on US equities or that the profile is based on SEC metadata, but overall it is sufficient.

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 coverage is 100% for the single parameter 'ticker', which already has a clear description. The description does not add extra meaning beyond the schema.

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 clearly states it provides a company profile assembled from SEC submissions metadata, which is a specific verb and resource. It distinguishes from sibling tools like stocks_filings or stocks_earnings that focus on individual filings or metrics.

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?

The description implies usage for obtaining a company profile but does not explicitly state when to use it versus alternatives like stocks_search or stocks_financials. No exclusions or prerequisites are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SiftingIO/siftingio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server