Skip to main content
Glama
Sign In

ClevSec EU compliance tools

by one.clevsec
OverviewDiscussionsAdmin

ISO 27001 remediation plan (ClevSec Pro)

iso27001_remediation_plan
Read-onlyIdempotent

Use after iso27001_gap_assessment when the user wants a plan towards ISO/IEC 27001 certification. Turns the same statuses into every gap with a recommended action, a priority, the Annex A control and a 30/60/90-day roadmap (organizational controls first). Requires ClevSec Pro.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "answers": "<answers>"
    },
    "name": "iso27001_remediation_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersYesControl question id to status, e.g. {"o1": "implemented", "t3": "planned"}. Unanswered controls count as gaps.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful context: the entitlement requirement ('Requires ClevSec Pro') and the shape of the generated plan. It doesn't discuss determinism or how unanswered controls beyond the schema note are handled.

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?

Two sentences, front-loaded with the usage trigger and followed by the output content. No filler or redundant restatement of the name or title.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the plan contents (action, priority, Annex A control, 30/60/90 roadmap) and the entitlement prerequisite. An agent has enough to call it correctly after the gap assessment.

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% and the schema's own description already explains the control-id-to-status map and that unanswered controls count as gaps. The description only echoes 'the same statuses' without adding format or syntax beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb and resource: it 'turns statuses into a plan' for ISO/IEC 27001 certification, listing concrete outputs (recommended action, priority, Annex A control, roadmap). It explicitly distinguishes itself from the sibling iso27001_gap_assessment by positioning itself as the downstream step.

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?

'Use after iso27001_gap_assessment when the user wants a plan towards ISO/IEC 27001 certification' gives both the sequencing prerequisite and the triggering intent. It also notes the plan prioritizes organizational controls first, which guides interpretation of output.

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

All ClevSec EU compliance tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources