recent_samplesMost recent samples in MalwareBazaar. Use the selector to pick a chunk size.
| Name | Required | Description | Default |
|---|---|---|---|
| selector | No | "time" (1h window) or "100" (last 100 samples). Default "100". |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of recent samples returned | |
| query | Yes | Query type used (get_recent) | |
| status | Yes | Query status (ok, no_results, or null) | |
| samples | Yes | Array of most recent samples |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "selector": "100"
+ },
+ {
+ "selector": "time"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of recent samples returned",
+ "type": "number"
+ },
+ "query": {
+ "description": "Query type used (get_recent)",
+ "type": "string"
+ },
+ "samples": {
+ "description": "Array of most recent samples",
+ "items": {
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "status": {
+ "description": "Query status (ok, no_results, or null)",
+ "enum": [
+ "ok",
+ "no_results",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "query",
+ "status",
+ "count",
+ "samples"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the description's claim of retrieving recent samples is consistent. It adds minor behavioral context (chunk size via selector) but does not disclose details like ordering or time window interpretation, which are partially in schema.
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 concise sentences with front-loaded purpose and no extraneous words. Every sentence provides value.
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 an output schema exists and annotations cover safety, the description is minimally adequate but lacks context about how recent samples are ordered or when to prefer this over siblings like 'get_sample_info' or 'search_tag'.
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 clear enum and default. The description adds only 'pick a chunk size', which adds minimal value beyond the schema. Baseline 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 provides 'most recent samples in MalwareBazaar', but does not explicitly use a verb like 'retrieves' or 'lists'. It is distinguishable from sibling tools like 'get_sample_info' or 'search_family' only by context; no differentiation is provided.
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?
No guidance on when to use this tool versus alternatives. The description only mentions using a selector for chunk size, without stating when not to use it or referring to sibling tools.
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.