abuse.ch Feodo Tracker botnet C&C IP blocklist
Four tools with explicit schemas and basic descriptions. All tools are READ_ONLY and stateless. However, descriptions are minimal (10-80 chars, well below the 194-char baseline), lack context on WHEN to use each tool, and parameter descriptions are sparse or missing. The 'list' tool has three optional parameters but only 'limit' has a meaningful constraint description. 'check_ip' lacks any parameter description. 'recent' and 'aggressive' have minimal guidance. No output schemas documented. Error handling is present in code (e.g., IPv4 validation, HTTP status checks) but not surfaced in tool descriptions. No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Naming is verb-forward (list, check, recent, aggressive) but 'aggressive' is vague, does not clearly convey 'fetch full aggressive blocklist'.
Full aggressive blocklist (includes older + lower-confidence IPs).
Check whether a given IPv4 is on the current blocklist.
Current C&C blocklist (optional malware-family / status filter).
Blocklist entries first seen in the last N hours.
Parameter descriptions missing or minimal. 'check_ip' ip parameter has no description. 'list' family and status lack guidance on valid values (e.g., are they case-sensitive? what are common examples?). 'recent' hours parameter lacks min/max constraints in description.
Output schemas not documented. Callers cannot predict response structure (e.g., does 'list' return {results: [...]} or {entries: [...]}?). LLMs must infer from code, risking misuse.
Tool descriptions too brief (10 - 80 chars vs. 194-char baseline). 'aggressive' (80 chars) and 'check_ip' (60 chars) lack context on when to use them vs. 'list'. No guidance on prerequisites or dependencies.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
No tool annotations. All four tools are read-only and idempotent, but lack readOnlyHint or idempotentHint annotations. LLMs cannot infer safety properties without explicit hints.
Vague tool name 'aggressive'. Does not clearly convey 'fetch full aggressive blocklist'. Better: 'list_aggressive' or 'get_aggressive_blocklist'.