Reuters Business and Financial News MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | 不适用 | |
| PORT | No | 不适用 | |
| API_KEY | Yes | API 密钥 |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_keywordsC | Get all Keywords |
| get_all_n2_tagsC | Get all N2 Tags |
| get_articles_by_date_and_author_idC | Get Articles by date and Author ID |
| get_all_subcategoriesC | Get all SubCategories |
| get_all_authorsB | Get all Authors |
| get_trending_newsD | Get articles by trends |
| get_articles_by_category_id_and_date_rangeB | Get Articles by categoryId and time period. This Endpoint has a hard limit set to max 20 result per page |
| get_articles_by_date_rangeC | Get Articles by time period. This Endpoint has a hard limit set to max 20 result per page |
| get_articles_by_keywordB | Get Articles by Keyword name Example of internal request: Where keyword_name like 'Microsoft%' |
| get_articles_by_keyword_u0026_date_rangeC | Get Articles by Date Range and Keyword name Example of internal request: Where keyword_name like 'Microsoft%' |
| get_markets_rics_by_asset_id_and_category_idD | Get Markets Rics by Asset ID and Category ID |
| get_rics_data_by_assetid_and_categoryidC | Get Rics Data By AssetId and CategoryId |
| get_all_market_categoriesB | Get all Market Categories |
| get_categories_by_market_asset_idC | Get Categories by market Asset id |
| get_all_tagsC | Get all tags |
| get_articles_by_dateB | Get Articles by Date This Endpoint has a hard limit set to max 20 result per page |
| get_all_market_assetsC | Get all Market Assets |
| search_keywordsB | Search a keyword by name Example of internal request: Where keyword_name like 'Microsoft%' |
| get_all_categoriesC | Get all Categories |
| get_article_by_category_id_and_dateC | Get Article by category id and article date ex :/api/v1/category-id-8/article-date-11-04-2021 category - category id from Category endpoint date-{day-month-year} |
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 20 tools
Most tools have distinct purposes: metadata retrieval vs. article queries with various filters. However, there is some overlap between keyword-related tools (get_all_keywords, search_keywords, get_articles_by_keyword) and between date filters (get_articles_by_date vs. get_articles_by_date_range), which could cause confusion.
The majority of tools follow a 'get_' prefix with descriptive names, like 'get_all_authors' or 'get_articles_by_date'. But there are minor inconsistencies: 'search_keywords' breaks the pattern, naming varies in casing (e.g., 'AssetId' vs 'asset_id'), and one tool has an encoded 'u0026' instead of 'and'.
With 20 tools covering various metadata and article queries, the count is well-scoped for a news/financial data API. Each tool serves a clear purpose without being excessive or minimal.
The tool set provides diverse query options (by category, date, keyword, author, etc.) but lacks a direct tool to fetch a single article by ID. Additionally, some endpoints have hard limits limiting result sets. The focus is read-only, but missing basic retrieval by article ID or full-text search.