Skip to main content
Glama

nist-standards__nist_control_family

List every NIST control in a family, the FedRAMP/800-53 control-family baseline. Use for "list all NIST access control controls", "NIST 800-53 AC family", "what controls are in identification and authentication", "NIST system and communications protection family". Input a family code ("AC", "IA", "SC", "AU", "SI", ...) or a family name ("access control"). Returns the family title plus every control id + title (including enhancements). Source: SP 800-53 Rev 5 (+ SP 800-171 Rev 3). Examples: {"fam

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": {
      "family": "AC"
    },
    "name": "nist-standards__nist_control_family"
  }
}

Input Schema

NameRequiredDescriptionDefault
familyYesFamily code ("AC","IA","SC",...) or name ("access control").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose return content (family title plus every control id + title, including enhancements) and provenance (SP 800-53 Rev 5, SP 800-171 Rev 3), which is valuable; however it says nothing about behavior on an unrecognized family value, ordering, or result size limits for large families.

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?

Well front-loaded: purpose, trigger phrases, input form, return shape, source. The four example queries are slightly redundant with one another and the trailing "Examples: {"fam" is truncated text that earns no place, but overall the structure is easy to scan.

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 tool with no output schema and no annotations, the definition covers input form, return contents, and data source adequately. The remaining gap is edge-case behavior (invalid family, pagination) rather than core calling information.

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 coverage is 100% and the schema already states 'family code ("AC","IA","SC",...) or name ("access control")'. The description repeats that dual-form input and adds only family examples, so baseline 3 is appropriate.

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?

States a specific verb and resource: "List every NIST control in a family" plus the baseline scope (FedRAMP/800-53). It is distinguishable from nist_control (single control) and nist_control_search by the word "every," though it never names those siblings explicitly.

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?

Provides explicit trigger phrasing ("Use for 'list all NIST access control controls'", "what controls are in identification and authentication"), which gives an agent clear context for selection. It stops short of exclusions or naming an alternative tool for single-control or keyword lookups.

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.