MCP Agent Sentinel
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_latest_news | Recupera as notícias e registros de dados mais recentes de IA por categoria, persona e limite. |
| search_ai_news | Pesquisa textual em tempo real no feed curado por palavras-chave ou modelos de IA. |
| get_niche_digestB | Gera um briefing/resumo executivo condensado e estruturado para um sub-nicho específico. |
| get_sources_statusA | Retorna o status atual de funcionamento e última execução dos scrapers e fontes de dados. |
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 generates executive briefings for niches, the other returns source status. No overlap.
Both tools use the consistent verb_noun pattern with 'get_' prefix, following a predictable convention.
With only 2 tools, the server feels severely under-scoped for a name implying 'Agent Sentinel' (monitoring agents). Expected more tools for a monitoring/management domain.
The tool surface is very thin: missing essential monitoring operations (e.g., list agents, pause/resume, view alerts). The niche digest tool seems out of place for a sentinel.