recent_iocsIOCs added to ThreatFox in the last N days. Useful for daily threat-intel ingestion.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Lookback days (1-7, default 3) |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of results returned | |
| query | Yes | The query type sent (get_iocs) | |
| status | Yes | Query status (ok, no_result, or null) | |
| results | Yes | IOCs added in the last N days |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "days": 3
+ },
+ {
+ "days": 7
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of results returned",
+ "type": "integer"
+ },
+ "query": {
+ "description": "The query type sent (get_iocs)",
+ "type": "string"
+ },
+ "results": {
+ "description": "IOCs added in the last N days",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "Query status (ok, no_result, or null)",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "query",
+ "status",
+ "count",
+ "results"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint as false, covering safety and idempotency. The description adds the source (ThreatFox) and the lookback window but does not detail behavior like pagination or ordering. It is consistent with annotations and adds some context.
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 two sentences, immediately front-loading the core action and resource. Every word is necessary; no repetition of schema information or superfluous details.
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 the low complexity (single optional parameter, output schema present), the description adequately covers the source, time range, and intended use case. It enables an agent to understand when and how to use the tool without missing critical information.
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 description coverage is 100%, with the 'days' parameter already described. The tool description does not add additional meaning beyond what the schema provides, so baseline score of 3 is appropriate.
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?
Description clearly states the tool returns IOCs added to ThreatFox in a configurable number of days. It specifies the resource (IOCs), source (ThreatFox), and temporal scope (last N days). This distinguishes it from sibling tools like search_ioc or recent_alerts.
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?
Description explicitly says 'Useful for daily threat-intel ingestion,' providing a clear use case. However, it does not specify when not to use or mention alternatives, though the context from sibling names suggests search_ioc might be for specific lookups.
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.