Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_scope_check

Read-onlyIdempotent

Checks a value or proposed executable call against an engagement's authorized targets and optional scope rules, then reports whether it matches without executing anything.

Instructions

Check one value against the engagement targets, or check a proposed executable call under optional scope enforcement. Reports the match without executing anything.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "engagement_id": "<engagement_id>"
    },
    "name": "oc_scope_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo
argumentsNo
executableNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description's 'Reports the match without executing anything' usefully confirms that supplying executable/arguments does not run them, which matters for a tool that accepts a command line, but it is partly redundant with readOnlyHint. It says nothing about behavior on a non-match (error vs. negative result) or about what 'optional scope enforcement' toggles.

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

Conciseness4/5

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

Two sentences, no filler, with the primary action front-loaded before the non-execution caveat. The phrasing is dense ('engagement targets', 'optional scope enforcement') but nothing is wasted.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the annotations cover safety. Still, for a 4-parameter tool with zero schema documentation, the description omits the required engagement_id and does not state whether a failed match raises an error or returns a negative result — gaps an agent would want closed before calling.

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?

With 0% schema description coverage, the description must carry the burden, and it does explain the semantics of three of four parameters: 'one value', 'proposed executable call', and 'arguments', plus the 'or' that signals value-mode and executable-mode are alternatives. The required engagement_id is never mentioned, and the exclusivity of value vs executable is implied rather than stated, which prevents a 5.

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 gives a specific verb ('Check') and two concrete modes: checking 'one value against the engagement targets' and checking 'a proposed executable call'. That maps cleanly onto the value vs executable/arguments parameters, so an agent can tell what the tool does without opening the schema. It stops short of naming how it differs from adjacent tools, which keeps it at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the second mode ('check a proposed executable call under optional scope enforcement') suggests this is a pre-flight gate before running a command, and 'optional' hints enforcement may be disabled. There is no explicit statement of when to prefer this tool over a sibling, nor any when-not guidance or prerequisite about engagement setup.

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

Deploy Server

Other Tools