Skip to main content
Glama

NS Pros MCP Gateway

nist-standards__nist_control_search

Keyword search across NIST 800-53 security/privacy controls and NIST 800-171 CUI requirements by title and requirement text. Use when the id is unknown, "NIST security control for least privilege", "NIST control about session lock", "NIST 800-53 encryption at rest", "NIST cybersecurity control multi-factor authentication", "access control / identification and authentication / system and communications protection". All query tokens must match (case-insensitive AND). Optional family filter (code l

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": {
      "query": "least privilege"
    },
    "name": "nist-standards__nist_control_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10).
queryYesKeywords, e.g. "least privilege" or "encryption at rest". All tokens must match.
familyNoOptional family filter: code ("AC","IA","SC",...) or name ("access control").

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, the description carries the burden and does disclose real behavior: matching is case-insensitive AND across all query tokens, and the search covers both title and requirement text rather than ids. It does not describe ranking/ordering of results or what fields come back, which leaves some behavioral gaps for a search tool.

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

Conciseness3/5

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

The purpose sentence and the AND-matching rule earn their place, but the long list of quoted example queries is repetitive filler, and the final sentence is cut off mid-word ('Optional family filter (code l'), leaving a dangling incomplete clause. Front-loading is good; the tail is wasteful and broken.

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?

For a three-parameter, single-required-field search with no output schema, the description explains what is searched and how matching works, but never says what a result contains or how many/which fields are returned. The truncated final clause further leaves the family-filter guidance incomplete.

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%, so the schema already documents query tokens, the default limit of 10, and that family accepts a code or a name. The description echoes that family is an optional filter over codes/names without adding any new constraint or format detail, so baseline 3 is correct.

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?

Opens with a specific verb+resource: keyword search across NIST 800-53 controls and NIST 800-171 CUI requirements, scoped to title and requirement text. It also implicitly separates itself from an id-based lookup ('Use when the id is unknown'), so an agent can pick it over nist_control without inspecting schemas.

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?

'Use when the id is unknown' gives a concrete trigger condition, and the sample queries demonstrate the intended phrasing for natural-language control lookups. It stops short of stating exclusions (e.g., when to prefer search_within or family browsing instead), so it is clear context rather than full when/when-not routing.

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.