tempo-insights
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 |
|---|---|
| tempo_searchA | Search Tempo.co reporting by a query. Returns article candidates with title, URL, date, description, and section when available. |
| tempo_articleA | Fetch one public Tempo.co article and return clean text plus normalized metadata. Use this before requesting a deep insight for a particular URL. |
| tempo_insightsB | Turn a Tempo.co article into a research brief: executive summary, key claims, named entities, timeline signals, numbers, uncertainties, and questions to investigate. It is extractive and explicitly separates reported facts from inferred themes. |
| tempo_compareA | Compare 2–5 Tempo.co articles. Highlights shared entities, repeated facts, differing framing, chronology, and reporting gaps. Useful for tracking a developing story. |
| tempo_auth_statusA | Report whether optional subscriber authentication headers are configured for Tempo fetches. Does not expose secrets. |
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 5 tools
Each tool has a clearly distinct purpose: search, fetch, generate insights, compare, and check auth status. No overlap or ambiguity exists between them, making tool selection straightforward for an agent.
All tools share the 'tempo_' prefix and use snake_case, but there's a mix of verb-led names (tempo_search, tempo_compare) and noun-led names (tempo_article, tempo_insights, tempo_auth_status). Minor inconsistency, but the pattern is still predictable and readable.
With exactly 5 tools, the set is well-scoped and each tool earns its place in the news analysis workflow. This falls comfortably within the ideal range for a specialized server.
The core workflow of searching, fetching, analyzing, and comparing articles is covered, plus a useful auth status check. Minor gaps like bulk fetching or topic discovery exist, but they are not critical to the server's purpose and can be worked around.