Skip to main content
Glama
Sign In
gmi-security-mcp

gmi-security-mcp

by Jayanng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scope_disable

Disable scope for a single repository and warn that scope-required tools will refuse to run if no scope policy exists.

Instructions

Disable scope for one repo.

Returns disabled with a warning that tools will now refuse if --require-scope is set, because there is no scope policy for the repo.

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": {
      "repo_path": "<repo_path>"
    },
    "name": "scope_disable"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.11

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose one genuinely useful behavioral fact: the call returns "disabled" with a warning and causes tools to refuse when --require-scope is set. It stops short of saying what configuration is modified, whether the change is reversible, or what permissions are needed for a mutation-style operation.

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 short sentences with the action front-loaded and no padding. The phrasing of the warning clause ("a warning that tools will now refuse if --require-scope is set") is slightly convoluted but still parseable.

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 description is sufficient to understand the high-level effect. However, for a state-changing operation with no annotations, the missing reversibility, permission, and parameter-format details leave meaningful gaps.

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

Parameters3/5

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

Schema description coverage is 0% for the single repo_path parameter, so the description must compensate. "for one repo" conveys that the operation is scoped to a single repository rather than global, but it adds nothing about the expected path format or resolution behavior beyond the schema's parameter name.

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 and resource: "Disable scope for one repo." An agent can tell this is the inverse of a scope-enable operation, but the sibling scope_enable is never named, so differentiation is left implicit.

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?

There is no when-to-use or when-not-to-use guidance, no mention of scope_enable as the alternative, and no stated prerequisites. The second sentence describes a consequence of the call rather than a condition for making it, so usage must be inferred entirely from the verb.

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