MacTech STIG

Get one STIG rule in full

get_stig_rule

Read-onlyIdempotent

Get the complete detail for one DISA STIG rule by its SV id (from search_stig): the requirement discussion, the exact check procedure an assessor runs, the fix text, severity, NIST control mapping, and whether it is SCAP-automatable. Call this when the user needs to implement or verify a specific rule.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sv_id`	Yes	Rule id, e.g. "SV-257777r991589_rule" (fragments matched if unique)

Output Schema

TableJSON Schema

Name	Required	Description
`sv_id`	Yes
`title`	Yes
`nist_id`	Yes	CCI identifier, e.g. CCI-000366.
`product`	Yes
`category`	Yes
`fix_text`	Yes
`severity`	Yes
`benchmark`	Yes
`check_text`	Yes	DISA's own check procedure - quote it rather than paraphrasing.
`description`	Yes
`automation_level`	Yes
`automation_source`	Yes
`severity_category`	Yes	CAT I / II / III, the vocabulary assessors use.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 9, 2026

changedOutput schema / properties / check_text / description

Previous value: -"DISA's own check procedure — quote it rather than paraphrasing."New value: +"DISA's own check procedure - quote it rather than paraphrasing."

Changed1 schema field changedAug 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "automation_level": {
+      "type": "string"
+    },
+    "automation_source": {
+      "type": "string"
+    },
+    "benchmark": {
+      "type": "string"
+    },
+    "category": {
+      "type": "string"
+    },
+    "check_text": {
+      "description": "DISA's own check procedure — quote it rather than paraphrasing.",
+      "type": "string"
+    },
+    "description": {
+      "type": "string"
+    },
+    "fix_text": {
+      "type": "string"
+    },
+    "nist_id": {
+      "description": "CCI identifier, e.g. CCI-000366.",
+      "type": "string"
+    },
+    "product": {
+      "type": "string"
+    },
+    "severity": {
+      "type": "string"
+    },
+    "severity_category": {
+      "description": "CAT I / II / III, the vocabulary assessors use.",
+      "type": "string"
+    },
+    "sv_id": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sv_id",
+    "nist_id",
+    "severity",
+    "severity_category",
+    "title",
+    "description",
+    "check_text",
+    "fix_text",
+    "product",
+    "benchmark",
+    "category",
+    "automation_level",
+    "automation_source"
+  ],
+  "type": "object"
+}

First observedAug 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, establishing safe read behavior. The description adds value by detailing exactly what content the user can expect (discussion, check, fix, severity, NIST mapping, SCAP-automatable), which sets proper expectations. No contradiction.

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?

The description is two sentences: the first states the action and output, the second gives the usage trigger. No wasted words.

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

Completeness5/5

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

For a one-parameter tool with an output schema, the description is complete. It provides purpose, usage context, and input-source guidance. No gaps remain.

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 schema covers the single parameter fully, and the description adds an important contextual clue that the sv_id originates from search_stig. This reinforces but slightly extends the schema, helping the agent know where to obtain the value.

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

Purpose5/5

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

The description uses the specific verb 'Get' with a clear resource 'one DISA STIG rule' and the method 'by its SV id'. It explicitly enumerates the detail fields returned, distinguishing it from sibling tool search_stig which presumably returns a list or summary.

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

Usage Guidelines4/5

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

The description includes the explicit trigger 'Call this when the user needs to implement or verify a specific rule' and mentions the source of the id '(from search_stig)'. It doesn't state explicit when-not scenarios or name alternatives, but the context is clear.

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

All MacTech STIG tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?