ai-daily-insights-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AI_DAILY_BASE_URL | No | Override the site origin (e.g. a preview deploy). | https://www.aidailyinsights.cn |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_latestA | List the most recent AI Daily Insights issues (date, title, one-line summary, tags, URLs). Start here to discover what is available. |
| get_latestA | Fetch the most recent issue, parsed into structured news items {index, title, signal, body}. Use this when the user asks for today's / the latest AI news and does not give a date. |
| get_articleA | Fetch a single daily issue by date, parsed into structured news items: each item has index, title, signal (the one-line judgment) and body. Date format: YYYY-MM-DD. |
| get_rangeA | Fetch every issue whose date falls within [from, to] (inclusive), each parsed into structured news items. Use for "the past week", "between X and Y", etc. Dates are YYYY-MM-DD. Issues are fetched in parallel. |
| list_by_tagA | List issues that carry a given tag (e.g. a company or topic like "OpenAI", "融资", "芯片"). Returns issue-level entries; use search() to find specific news items by keyword. |
| searchA | Full-text + tag search across all news items. Provide a keyword query, a tag, or both. Returns matching items with date, title, signal and a short snippet. Backed by the site search endpoint (one call); falls back to the flat index if unavailable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: fetching by date, latest, range, listing by tag, listing latest issues, and full-text search. There is minor overlap between list_latest and get_latest, and between list_by_tag and search, but descriptions clarify the differences (issue-level vs. item-level).
All names use lowercase snake_case and follow a verb-based structure. However, the pattern is mixed: get_article, get_latest, get_range are consistent; list_by_tag and list_latest use 'list', and search is a bare verb. This is minor inconsistency overall.
With 6 tools, the count is well-scoped for a news retrieval service. Each tool covers a specific access pattern (by date, latest, range, tag, list, search), and none feel redundant or out of place.
The tool surface covers the main ways to retrieve articles: by date, latest, range, tag listing, and full-text search. A notable gap is the lack of a tool to list all available tags, which would assist in using list_by_tag and search effectively.