Google News MCP Agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ingest_newsA | Fetches news articles from Google News for a given topic, generates vector embeddings, and stores them in a local ChromaDB database. |
| search_newsC | Searches the stored news articles using semantic search. |
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 2 tools
The two tools have clearly distinct purposes: one fetches and stores news, the other searches stored articles. No overlap exists.
Both tools follow the verb_noun pattern consistently: ingest_news and search_news.
Two tools is minimal but appropriate for the narrow scope of fetching and searching news. It's slightly thin but not excessive.
The tools cover the basic workflow of ingesting and searching, but lack operations like deleting stored articles or listing topics, which are minor gaps.