List Hack The Box machines with filters by difficulty, state, status, keyword, and sort options.
List machines with optional filters. difficulty/state accept comma-separated values.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| todo | No | ||
| state | No | ||
| status | No | ||
| keyword | No | ||
| sort_by | No | ||
| per_page | No | ||
| sort_type | No | ||
| difficulty | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description only mentions filters; does not disclose pagination, rate limits, or any 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?
Single sentence is concise and front-loads purpose; could be restructured to include more info without losing conciseness.
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?
No output schema, 9 parameters, no annotations; description lacks return values, pagination details, and filter behavior beyond comma-separated values.
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 0%, but description only adds meaning for difficulty and state; other 7 parameters are not explained.
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?
Clearly states 'List machines' with optional filters, but does not differentiate from siblings like htb_recommended_machines or htb_active_machine.
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 vs. alternatives; only implies filtering via comma-separated values.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AeonDave/htb-app-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server