Search a small curated atlas of agent-useful APIs, self-hosted tools, payment rails, scraping helpers, and automation primitives.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| category | No | Optional category filter |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries full burden for behavioral disclosure. It only says 'search', implying non-destructive behavior, but lacks details on return format, pagination, authorization needs, or other behavioral traits.
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?
The description is a single sentence, concise and to the point. It could be slightly more efficient, but it carries necessary information without fluff.
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?
Given no output schema and no annotations, the description does not fully cover what to expect from results or how to use the tool effectively. It is too brief for a search tool that presumably returns a list of resources.
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 descriptions for both parameters. The description adds no additional meaning beyond the schema, which is sufficient but not enhanced.
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 the tool searches a curated atlas of agent-useful resources, specifying categories like APIs, self-hosted tools, payment rails, etc. This differentiates it from sibling tools that are specific endpoints.
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?
The description does not explicitly state when to use this tool versus siblings. However, the context of a curated atlas implies it is for discovering relevant tools among many, but no explicit guidance is provided.
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.
Tools cover very diverse domains (weather, FDA, legal, crypto, etc.), so cross-domain confusion is low. However, within domains there is notable overlap: multiple food recall tools (food_recall_check, food_safety), multiple weather tools (weather_current_global, weather_forecast_grid, weather_alerts, weather_bias), and several Polymarket-related tools. This can cause agent misselection.
Naming is inconsistent: some tools use verb_noun (search_arxiv, scrape, validate_agent_manifest), others use noun phrases (smart_money, space_weather, tide_data), and some are long descriptive phrases (cross_platform_arb_scan, polymarket_event_scan). No single pattern is followed, making predictions difficult.
95 tools is excessively high for any coherent purpose. The server appears to be a random aggregation of APIs with no clear scope. Such a large catalog overwhelms agents and dilutes utility; most tools could be split into specialized servers.
Although many domains are touched, each is covered only shallowly. For example, weather lacks historical data, legal lacks case details beyond court opinions, and financial lacks stock prices. There are obvious gaps like no user authentication or data persistence. The tool set feels like a collection of endpoints rather than a cohesive service.