Skip to main content
Glama
SiftingIO

siftingio-mcp

Official

Search stocks

stocks_search
Read-only

Search for stocks by ticker, company name, or CIK substring. Retrieve matching tickers and company details.

Instructions

Ticker/company lookup by ticker, name, or CIK substring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch string: ticker, company name, or CIK substring.
limitNoMax results, default 25, max 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
metaYes
Behavior3/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds that it searches by substring, which is mildly informative but doesn't disclose rate limits, pagination, or data freshness. Moderate added value.

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?

The description is a single, clear sentence with no unnecessary words. It efficiently conveys the tool's purpose and parameter usage.

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?

Given the tool's simplicity (2 params, read-only, output schema present), the description covers the essential purpose and parameter hints. It doesn't detail return values, but the output schema handles that. Adequate for a search tool.

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%, and the description's explanation of parameters ('ticker, company name, or CIK substring' for q, and limit details) largely mirrors the schema field descriptions. No additional semantic insights 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 the verb 'lookup' and the resource 'stocks/tickers', specifying the search methods (ticker, name, CIK substring). It distinguishes from sibling tools like stocks_profile or stocks_bars which serve different purposes.

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 searching stocks but does not explicitly mention when to use this tool over alternatives or provide exclusions. No guidance on prerequisites or complementary tools.

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