Skip to main content
Glama
v587d

Insights Knowledge Base MCP Server

by v587d

search_report_profile

Retrieve aggregated overviews of insight reports by querying with multiple conditions such as keywords, title, content, publisher, and date range. Get detailed profiles including download links and matched keywords.

Instructions

该方法用于查询多条件组合的报告整体概况。LLM需根据用户输入的消息(user_message)提炼出以下参数。 ️⚠️注意:当LLM引用该方法返回的结果时,必须用markdown格式明确、醒目告知用户引自哪篇报告和具体访问地址! 比如“观点引自《Open source technology in the age of AI》。(查看完整报告)[<如果"download_url"不为空,填入download_url>]” !!!注意每份报告单独列举 download_url,不要笼统指向某一个可能不存在的地址。

参数:
    keywords: List[str] = None, 整篇报告的关键词。
    title: str = "", 报告标题包含词。
    content: str = "", 报告内容包含词。
    publisher: str = "", 报告发布者。
    start_date: Optional[datetime] = None, 报告查询开始日期。
    end_date: Optional[datetime] = None, 报告查询结束日期。
    match_logic: str = "OR", 匹配逻辑。"OR" 或者 "AND",二选一,**优先用 "OR"**。

返回:
    results:报告概览
      - file_name: 报告名称
      - topic: 报告主题
      - content: 报告整体摘要
      - published_by: 发布机构
      - published_date: 发布日期
      - local_path: 报告存放于本地地址
      - download_url: 报告网络链接
      - matched_keywords: 匹配关键词组
    current_page:当前页码。⚠️当前页码小于总页码时,LLM需在结尾处提示用户可输入“下一页”查询更多记录。
    total_pages: 总页数
    total_matches: 总匹配记录条数

LLM需将该方法返回结果组织成通畅的语言传达给用户。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
contentNo
end_dateNo
keywordsNo
publisherNo
page_indexNo
start_dateNo
match_logicNoOR
Behavior3/5

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

No annotations provided, so description must carry the burden. It discloses that it's a read-only search and pagination behavior, but doesn't mention authentication, rate limits, or side effects. Adequate but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is lengthy and mixes parameter definitions, usage instructions, and output format. While structured, it could be more concise. The markdown citation instructions add verbosity.

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 8 parameters and no output schema, the description covers the return structure, pagination, and parameter usage. It lacks error handling or no results guidance, but is fairly complete for an LLM-oriented tool.

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?

The description explains most parameters (keywords, title, content, publisher, dates, match_logic) with details like default and priority for match_logic. The page_index parameter is not described, but the overall coverage is high.

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 tool is for querying overall report profiles with multiple conditions. It distinguishes itself from sibling tools like search_content_detail by focusing on summary profiles.

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?

The description provides explicit instructions for LLM to extract parameters from user messages, and how to cite results and handle pagination. It does not explicitly state when not to use, but the context is clear.

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/v587d/InsightsLibrary'

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