Skip to main content
Glama
MarkAC007

mcp-server-scf

by MarkAC007

scf_create_risk

Create a new risk assessment in the risk register, using likelihood and impact scores to populate the 5×5 risk matrix.

Instructions

Create a new risk assessment in the risk register (write — editor+ role). Likelihood and impact scores populate the 5×5 risk matrix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerNoName or identifier of the risk owner
titleYesRisk title (required, max ~100 chars)
impactYesInherent impact on a 1–5 scale
org_idYesOrganization UUID — obtain from scf_list_organizations
control_idNoSCF control ID to link (e.g., 'AST-01') — obtain from scf_list_controls
likelihoodYesInherent likelihood on a 1–5 scale
descriptionYesRisk description (required)
treatment_statusNoTreatment status: 'mitigate', 'accept', 'transfer', or 'avoid'
Behavior3/5

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

Discloses it is a write operation requiring editor+ role. States that likelihood and impact populate the 5×5 matrix. Lacks details on side effects, auto-calculation, or response format. With no annotations, more transparency expected.

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?

Single sentence with a parenthetical. Front-loaded with action. Could be slightly clearer on the parenthetical format, but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Does not explain what happens upon creation (e.g., returns risk ID, triggers any workflow). No output schema provided, so description should at least hint at response. Missing details for a creation tool with 8 parameters.

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

Parameters4/5

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

Schema covers all 8 parameters with descriptions (100% coverage). Description adds context that likelihood and impact together determine the risk matrix cell. Useful beyond schema alone.

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?

Clearly states action ('create') and resource ('new risk assessment in the risk register'). Includes role requirement. However, does not differentiate from sibling scf_create_custom_risk, which could cause confusion.

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?

Mentions required role ('editor+') and that it writes to the risk register. No explicit guidance on when to use this vs. scf_create_custom_risk or other risk tools. Implies use for standard risk matrix entries.

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/MarkAC007/mcp-server-scf'

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