Skip to main content
Glama

get_scope

Check the configured scan scope, limits, and intrusive-script status to confirm permitted targets and actions before running an Nmap scan.

Instructions

Show the configured scan scope, limits, and whether intrusive scripts are enabled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the burden. "Show" implies a read-only operation, and the text discloses the three categories of configuration that are surfaced, including whether intrusive scripts are enabled — useful context for deciding whether a scan will be aggressive. It does not confirm non-mutation, permissions needed, or whether the values can be changed here, which for a zero-annotation tool is a moderate gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no waste, front-loaded on the verb and the returned configuration, with the most decision-relevant detail (intrusive scripts enabled) placed last for emphasis. Nothing is repeated from structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with an output schema, the description covers what an agent needs: it is a configuration readout and it tells you what kinds of facts come back. With no annotations and an output schema handling return-value detail, only a note about read-only semantics or prerequisites is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly avoids inventing arguments for a zero-arg call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ("Show") and a specific resource (the configured scan scope), plus enumerates what is included: limits and the intrusive-script flag. That distinguishes it from scanning siblings such as get_scan or port_scan, which act on targets rather than reading configuration, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no exclusions, and no mention of alternatives among the many scan/audit siblings. An agent must infer that this is the configuration-inspection call to make before launching a scan; nothing in the text states that or says when it should be preferred over get_scan or list_scans.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.