Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__nist_control

Look up the full text of one NIST 800-53 security control or NIST 800-171 CUI security requirement by id, the control statement (requirement prose), discussion/guidance, and related controls. Use for "what does NIST control AC-2 require", "NIST 800-53 AC-2 access control", "FedRAMP control SC-7 boundary protection", "NIST authenticator management IA-5", "NIST CUI control 800-171 3.1.1". Forgiving id: accepts "AC-2", "ac-2", "AC-02", control enhancements "AC-2(1)" or "AC-2.1", and CUI ids "3.1.1"

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "AC-2"
    },
    "name": "nist-standards__nist_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesControl id, e.g. "AC-2", "ac-2", "AC-02", "SC-7", "IA-5", enhancement "AC-2(1)"/"AC-2.1", or CUI requirement "3.1.1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 does disclose the content returned (statement, discussion/guidance, related controls), and 'look up the full text' clearly frames it as a non-mutating read. It is silent on edge behavior that matters here: what happens for an unknown id, whether an enhancement like AC-2(1) also returns the base AC-2 text, and whether a bare family id ('AC') is accepted.

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?

Structure is well front-loaded: purpose and returned fields first, then usage examples, then id format. The trailing 'Forgiving id' sentence duplicates the input schema's examples and could be cut without loss, but the example-query list earns its length by improving retrieval matching.

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 one-parameter read-only lookup with no output schema and no annotations, the definition covers purpose, payload contents, and accepted id forms — enough to invoke it correctly. Remaining gaps (not-found behavior, enhancement-to-parent inheritance, family-level ids) are modest for this complexity level.

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 100% and the schema's id description already lists the identical accepted forms ('AC-2', 'ac-2', 'AC-02', 'AC-2(1)'/'AC-2.1', '3.1.1'), so the 'Forgiving id' sentence largely restates structured data rather than adding meaning. It adds no new semantic detail such as valid-range boundaries, case/zero-padding normalization rules, or failure behavior, so the high-coverage baseline of 3 applies.

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 opens with a specific verb and resource — 'Look up the full text of one NIST 800-53 security control or NIST 800-171 CUI security requirement by id' — and enumerates the returned payload (control statement, discussion/guidance, related controls). The word 'one' plus 'by id' implicitly separates it from a search or family-listing operation, but the actual sibling tools (nist_control_search, nist_control_family) are never named, so the differentiation is only implied.

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 'Use for ...' clause supplies five concrete example queries spanning 800-53, FedRAMP, IA-5 authenticator management, and 800-171 CUI, which gives strong positive when-to-use signal. It stops short of any when-not guidance — e.g. no pointer to nist_control_search for keyword/topic lookup or nist_control_family for enumerating a family — so an agent must infer the routing boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.