Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

stock-feed

Search cross-platform trending stock content by keyword to discover viral posts and analyze market sentiment. Filter results by platform and date for targeted insights.

Instructions

股票内容资讯查询,跨平台搜索股票相关爆款内容

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateNo结束日期 YYYY-MM-DD
keywordYes搜索关键词(如股票代码或名称)
platformsNo平台列表(逗号分隔)
startDateNo起始日期 YYYY-MM-DD

Schema Changelog

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

  1. First observedv1.0.4

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It signals read-only behavior via '查询' and an output focus on '爆款内容', but it does not disclose return format, platform coverage, pagination, freshness, or limitations.

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?

One sentence with no filler and the core operation front-loaded. There is mild redundancy between '股票内容资讯查询' and '跨平台搜索股票相关爆款内容', but it remains concise and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no annotations and no output schema, so the description should explain what the returned content looks like and which platforms are included. It only says 'content info query' and 'viral content', leaving the agent to guess return structure and cross-platform scope.

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%, so the baseline is 3. The description adds no parameter-specific detail beyond the stock-content theme; it does not clarify platform values, date formats, or keyword behavior beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific operation: querying stock-related news/content and cross-platform search for viral stock content. It distinguishes itself from platform-specific feed siblings and stock-analysis, though it does not explicitly name an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is provided. The cross-platform phrasing implies one usage context, but with many similar search/feed siblings, there is no explicit comparison or exclusion.

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/if530770/redfox-mcp'

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