Skip to main content
Glama
konstruktoid

prescryb

by konstruktoid

lookup_cce

Find NIST Common Configuration Enumeration entries for a target platform. Filter by keyword or CCE ID to identify security configuration recommendations for compliance mapping.

Instructions

Look up NIST Common Configuration Enumeration entries for a platform.

`target`: free text naming a platform, resolved against the export
names published by https://github.com/konstruktoid/cce-web (NIST itself
only publishes CCE as spreadsheets). For a host from inventory_host, use
'rhel<major version>' for any RHEL-family distro_id (rhel, almalinux,
rocky - CCE only tracks the upstream RHEL number) or
'SLES<major version>-DISA-STIG' for suse; Debian, Ubuntu, Alpine, and
Arch have no CCE coverage upstream at all. Call list_cce_targets to see
every published platform (also covers e.g. 'firefox', 'apache-httpd2.2',
'win2k8r2').

Pass `keyword` (matched against title/description/rationale/config
group) or `cce_id` (exact ID, e.g. 'CCE-80876-6') to filter results.
Without either, only the platform's config-group categories and entry
count are returned - dumping an entire platform (hundreds of entries)
isn't useful; narrow with a keyword first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cce_idNo
targetYes
keywordNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations exist, so description covers the behavior: returns filtered entries or categories/count, explains target resolution, and warns against dumping entire platform. Safe read operation implied.

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?

Multiple paragraphs but each sentence adds value. Structured with summary line, target details, and filtering options. Could be slightly more concise but not wasteful.

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?

Given 3 params, no annotations, but output schema exists. Explains behavior with and without filters, covers main use cases. Lacks mention of error handling or missing targets, but overall adequate.

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

Parameters5/5

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

Schema has 0% description coverage; description compensates fully by detailing target formation (examples, resolution), keyword matching fields, and cce_id with example. All three parameters are well explained.

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 explicitly states it looks up NIST CCE entries for a platform, using specific verbs and resource. It distinguishes from siblings like list_cce_targets and check_cves.

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 clear guidance on when to use target, keyword, cce_id, and directs to list_cce_targets for platform discovery. Implicitly covers when not to use by explaining behavior without filters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/konstruktoid/prescryb'

If you have feedback or need assistance with the MCP directory API, please join our Discord server