Skip to main content
Glama

postrc_configure

Idempotent

Set validation policy before running scans: select modules, set block thresholds, suppress known false positives, and configure compliance checks (monitoring, legal) to match your risk tolerance.

Instructions

[Pro] OPTIONAL - configure validation policy BEFORE running postrc_scan. Sets: which modules are active (security, monitoring, legal-claims, legal-product), whether to block on critical/high findings, CWE suppressions (known false positives), monitoring requirements, and legal review settings (Pro tier: product domain, jurisdiction, license/accessibility checks). Defaults are reasonable - only call this if the user has specific compliance or risk tolerance requirements. Saved to post-rc/ state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modulesNoActive validation modules
jurisdictionNoJurisdiction for compliance checks (e.g., eu triggers GDPR checks)
project_nameNoProject name
project_pathYesAbsolute path to the project directory
block_on_highNoBlock deployment on High findings
legal_enabledNoEnable legal review modules
check_licensesNoCheck dependency license compliance
product_domainNoProduct domain for regulatory detection (e.g., healthcare triggers HIPAA checks)
suppressed_cwesNoCWE IDs to suppress
block_on_criticalNoBlock deployment on Critical findings
edge_case_enabledNoEnable edge case analysis module (Pro tier)
require_analyticsNoRequire analytics instrumentation
legal_claims_auditNoEnable framework claims audit (self-audit)
app_security_skillsNoAudit skills to run: 1=Auth+Abuse, 2=AuthZ+RLS, 3=Validation, 4=Search+Query, 5=Admin
check_accessibilityNoCheck accessibility compliance (ADA/WCAG)
legal_product_auditNoEnable product legal review
app_security_enabledNoEnable application security auditor module
edge_case_categoriesNoEdge case categories to scan (default: all)
require_error_trackingNoRequire error tracking instrumentation
edge_case_block_on_criticalNoBlock ship gate on critical edge case findings
app_security_block_on_criticalNoBlock ship gate on critical app security findings
Behavior4/5

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

Annotations indicate idempotent and non-destructive behavior. The description adds useful context: persistence to 'post-rc/ state' and that defaults are reasonable, implying calling it changes state. No contradictions with annotations.

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

Conciseness5/5

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

Three sentences, front-loaded with '[Pro] OPTIONAL', and every sentence carries essential information (what it sets, when to use, state persistence). No filler.

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?

With 21 parameters and no output schema, the description provides enough high-level context for an agent to understand when and why to invoke this tool. It does not enumerate all parameters, but the schema does; the description's grouping is sufficient for this configuration tool.

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?

Input schema covers all 21 parameters with descriptions (100% coverage), so baseline applies. The description groups parameters into categories (modules, blocking, suppressions, etc.) but adds no detail beyond schema.

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 clearly states the tool's function: 'configure validation policy BEFORE running postrc_scan'. It specifies the resources affected (modules, block thresholds, CWE suppressions, monitoring, legal review) and distinguishes it from siblings by noting its optional, pre-scan nature.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'OPTIONAL... BEFORE running postrc_scan' and when not to: 'Defaults are reasonable - only call this if the user has specific compliance or risk tolerance requirements.' This provides clear guidance without ambiguity.

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/originalrashmi/rc-engine-product-framework'

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