check_tool_statusCheck whether an AI tool is still alive. Returns active, deceased, or acquired — with the date and cause if it shut down, and live alternatives if it did. Use this before recommending a tool to avoid suggesting one that no longer exists.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | Yes | Tool name or directory slug to check, e.g. "Jasper" or "jasper-ai". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds details on returned fields (status, date, cause, alternatives) beyond annotations. No contradictions.
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?
Three sentences, no fluff. Action, output, and usage guidance are all front-loaded.
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?
Complete for a simple read-only tool with full annotations and single parameter. No gaps.
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?
Schema coverage is 100% with example. Description does not add extra meaning beyond what schema provides.
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?
Verb 'check' and resource 'AI tool status' are clear. Distinguishes from siblings like get_tool (details) or list_tools (list all).
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 recommends use before recommending a tool. Does not mention when not to use, but context is clear.
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.
Each tool has a distinct purpose: checking status, comparing two tools, finding alternatives, getting a full profile, listing by category, and searching. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (check_tool_status, compare_tools, find_alternatives, etc.), making it predictable.
6 tools are well-scoped for a directory server, covering discovery, lookup, comparison, and status checks without being too few or too many.
The tool set fully covers user needs: search, list, get details, compare, find alternatives, and check lifecycle status. No obvious gaps for the intended purpose.