Fetches operational status of major dev infrastructure (GitHub, Cloudflare, Discord, OpenAI, Vercel, npm, Reddit, Atlassian, Anthropic). Cache TTL 60s. Use when the agent needs to know if a dependency is up or to explain a recent outage.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and openWorld hints. The description adds useful behavioral context, specifically the 60-second cache TTL, and lists the services covered. It does not describe return format or error handling, but this is a simple fetch tool and the cache detail is valuable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action, and no wasted words. All information is relevant and efficiently presented.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple no-parameter, no-output-schema tool, the description provides complete context: purpose, usage, and cache behavior. It adequately covers what the agent needs to know to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has zero parameters, so the baseline is 4. There are no parameter semantics to add, and the description appropriately omits any parameter discussion.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action ('Fetches operational status') and resource ('major dev infrastructure') with a list of services, distinguishing it from sibling tools that focus on other domains like crypto, weather, and AI stack CVEs.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly provides when to use: 'Use when the agent needs to know if a dependency is up or to explain a recent outage.' This is clear context and no alternative tool is needed since siblings are unrelated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes (e.g., tf_btc_price vs tf_fear_greed), but there is some overlap between free and premium aggregated tools (e.g., tf_briefing, tf_premium_briefing, tf_premium_agent_context). However, descriptions explicitly differentiate them by content and cost.
All tools follow a consistent pattern: 'tf_' prefix (with 'tf_premium_' for premium ones) and snake_case. Names are descriptive and predictable, e.g., tf_btc_price, tf_earthquakes, tf_premium_macro.
27 tools is on the high side, but the server covers a broad domain (crypto, finance, earthquakes, AI trends, payment system, etc.). Each tool serves a specific purpose, so the count is borderline acceptable but feels slightly heavy.
The tool surface covers a wide range of data feeds: crypto, forex, macro indicators, earthquakes, HN, HuggingFace, prediction markets, payment system, and service status. Minor gaps exist (e.g., no dedicated stock prices tool beyond premium macro, no weather), but overall it's comprehensive for a terminal feed.
