Skip to main content
Glama
mcp-server-scf

mcp-server-scf

by MarkAC007

scf_catalog_read

Read-only

Read SCF reference catalog data by method—list or get controls, domains, frameworks, assessment objectives, and evidence definitions—to look up compliance details without organization scope.

Instructions

Read the SCF reference catalog (no org): controls, one control with its objectives and evidence, domains, frameworks, assessment objectives, evidence definitions. Pick with method.

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1–100, default 25) Used by: list_controls, list_assessment_objectives, list_evidence.
domainNoSCF domain code (e.g., 'GOV', 'AST', 'IAC') — obtain from scf_list_domains Used by: list_controls.
methodYeslist_controls: List SCF security controls from the reference catalog. Returns paginated controls with SCF ID, title, description, and mapped frameworks. Filter by domain, framework, or free-text search. get_control: Get a single SCF control by ID. Returns description, mapped frameworks, assessment objectives, and linked evidence items from the reference catalog. list_domains: List every compliance domain in the SCF taxonomy. Domains group related controls (e.g., GOV = Governance, AST = Asset Management, IAC = Identity & Access Control). get_domain: Get one SCF domain with its controls (read, no org). Deprecated controls are excluded unless include_deprecated is set; a deprecated domain still resolves, badged. list_frameworks: List every compliance framework mapped in the SCF catalog (NIST 800-53, ISO 27001, SOC 2, FedRAMP, GDPR, and 350+ more). Returns framework identifiers and display names. list_assessment_objectives: List SCF assessment objectives — the 5,736 test criteria used to evaluate control implementation. Optionally filter by control ID; supports free-text search and pagination. list_evidence: List the SCF reference catalog's 272 evidence types (read, no org). control_mappings is the catalogue-wide mapping, not scope — see scf_get_evidence_requiring_controls. Free-text search, pagination. get_evidence: Get one catalog evidence entry (read, no org): title, description, area of focus, control_mappings — the catalogue-wide mapping, not scope. In-scope requirers: scf_get_evidence_requiring_controls.
offsetNoPagination offset — number of results to skip (default 0) Used by: list_controls, list_assessment_objectives, list_evidence.
scf_idNoSCF control identifier in DOMAIN-NN format (e.g., 'AST-01', 'IAC-15', 'GOV-02') Used by: get_control.
searchNoFree-text filter applied to control title and description [list_controls] | Free-text filter applied to objective text [list_assessment_objectives] | Free-text filter applied to evidence title and description [list_evidence] Used by: list_controls, list_assessment_objectives, list_evidence.
frameworkNoFramework slug (e.g., 'nist-800-53', 'iso-27001') — obtain from scf_list_frameworks Used by: list_controls.
control_idNoLimit to one SCF control in DOMAIN-NN format (e.g., 'GOV-01', 'AST-02') Used by: list_assessment_objectives.
identifierNoDomain code or slug, e.g. 'IAC' — obtain from scf_list_domains Used by: get_domain.
evidence_idNoCatalog evidence ID, e.g. E-IAM-01 — obtain from scf_list_evidence_catalog Used by: get_evidence.
include_deprecatedNoInclude catalog rows deprecated by a later SCF version. Default false — the catalog answers with active rows only, and deprecated rows carry a lifecycle badge when included. [list_controls, list_domains, list_assessment_objectives, list_evidence] | Include deprecated controls (default false) [get_domain] Used by: list_controls, list_domains, get_domain, list_assessment_objectives, list_evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.1.0

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the description's main contribution is the catalog-versus-org scoping note and the hint that a single-control read returns objectives and evidence. It does not disclose pagination behavior, result caps, or deprecated-row handling beyond what the schema enumerates. Useful but not rich behavioral context.

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?

A single compact sentence with the resource and scope front-loaded and the operation list following. Every clause maps to real functionality. It is dense list-style prose but has no filler sentences.

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 an 11-parameter, eight-method multiplexed tool with no output schema, the description is thin; most of the actionable detail lives in the method enum descriptions rather than the top-level description. It is adequate because the schema compensates, but the description alone would not tell an agent enough about method-specific behavior.

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%, including per-method descriptions and per-parameter 'Used by' mappings, so the schema carries parameter semantics. The description adds the dispatch pattern ('Pick with method') but no parameter format or constraint detail beyond the schema. Baseline 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 names a specific verb and resource ('Read the SCF reference catalog') and enumerates the object types available (controls, single control with objectives/evidence, domains, frameworks, assessment objectives, evidence definitions). The '(no org)' qualifier is a meaningful scope distinction against the org-scoped sibling tools, though no sibling is named explicitly and the agent must infer that scf_control_read / scf_evidence_read are the org-scoped counterparts.

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

Usage Guidelines3/5

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

'Pick with method' tells the agent how the operation is selected but gives no when-to-use versus when-not guidance, and no explicit routing to the sibling read tools for org-scoped data. The '(no org)' hint implies the alternative exists without stating it, leaving usage selection to inference from the name and the method enum.

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