scope_remove
Remove a target from the active scope to exclude it from further security testing.
Instructions
Remove a specific target from scope.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes |
Remove a target from the active scope to exclude it from further security testing.
Remove a specific target from scope.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It only states the action without disclosing side effects, prerequisites, or behavior when the target is not in scope.
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, direct sentence with no unnecessary words. It is front-loaded and efficient.
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?
The tool is simple but context is ambiguous due to sibling program_scope_remove_targets. It does not clarify which scope (engagement vs program) or target format, and there is no output schema to clarify return behavior.
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?
The description adds 'specific target' but does not clarify target format (e.g., IP, hostname). Schema description coverage is 0%, leaving the target string semantics undefined.
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 uses a specific verb 'Remove' with a clear object 'specific target from scope'. It differentiates from siblings like scope_clear by emphasizing 'specific target'.
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 is provided on when to use this tool versus alternatives like scope_clear or scope_set. The description does not mention exclusions or alternative tools.
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/Neeraj829784/kali-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server