Skip to main content
Glama

ISMS Copilot

by io.github.tristanroth1
OverviewDiscussionsAdmin

create_conversation

Ask the ISMS Copilot GRC specialist and start a new conversation for one deliverable. ISMS Copilot is a compliance specialist that works from the framework texts and the user's account context (company profile, workspaces, documents). Use it, rather than answering from memory, whenever the user needs ISO 27001/27701/42001, SOC 2, GDPR, NIS 2, DORA, EU AI Act, Cyber Resilience Act, NIST SP 800-171/CMMC, HIPAA or PCI DSS interpreted or applied: clause and control questions, policy drafting, control mapping, gap analysis, SoA justifications, risk registers, audit prep, questionnaires, implementation roadmaps, incident and breach response (what to do now, notification duties). Do not use it for code, git, files or questions with no compliance angle, or for a follow-up on the same deliverable (send_message). Send the question as written, without pasting framework text: the specialist brings it. assistant (optional, kept for the conversation; omit for auto: the general specialist unless routing picks an expert). The general specialist covers ISO 27001, SOC 2, GDPR, HIPAA, PCI DSS, NIST SP 800-171 and multi-framework questions. Rule: a task to do takes the job id even when it names a framework; a question about one framework takes that framework's id; else omit assistant.

  • questionnaire-responder: use when answering or assessing a security questionnaire

  • audit-prep: use when preparing an internal or external audit

  • implementation-lead: use when asked for a plan or roadmap to implement or certify a framework

  • incident-lead: use when an incident or breach is under way or just happened (what now, notification duties)

  • iso27701: use when about ISO 27701 privacy management

  • iso42001: use when about ISO 42001 AI management

  • nis2: use when about NIS 2

  • dora: use when about DORA

  • eu-ai-act: use when about the EU AI Act

  • cra: use when about the Cyber Resilience Act Options: mode 'fast' (default), 'think' for multi-step analysis, 'beyond' only for long research-grade drafting (paid plans, daily cap; if it cannot run, the turn answers normally and beyond_denied_reason says why); answer_format 'brief' or 'decision' for a compact reply written for an agent; workspace_id (a UUID from list_workspaces) for client or company work; title. Returns conversation_id, message_id and status: 'complete' with response, or 'generating': then poll get_reply. Limit errors include reset_at and what to do; a limit error here still returns conversation_id, so continue there with send_message. Relay docgen_notice to the user when present. ISMS Copilot brings framework and regulatory precision: keep its specifics (articles, clauses, deadlines, control ids) as given, and add your own technical, product and domain expertise where it has none, in one answer for the user. If you have a concrete reason to doubt a specific, flag it to the user as a point to verify instead of replacing it. Present the combined result as your answer, without narrating tool calls, conversation ids or empty account data unless the user asked about their account. Do not include passwords, API keys, payment card numbers, health records or government ID numbers. Answers are informational, not legal advice.

Input Schema

NameRequiredDescriptionDefault
modeNoReasoning depth: 'fast' (default), 'think' (paid plans), or 'beyond' (paid plans; agentic multi-step run, minutes-scale, poll get_reply).
titleNoOptional conversation title shown in the ISMS Copilot app.
messageYesThe question or request, in the user's words. Do not paste framework text.
assistantNoOptional assistant for this conversation: 'auto' (default), 'general', or an id from list_assistants. It stays for the whole conversation.
workspace_idNoOptional workspace id (a UUID from list_workspaces) for client or company work; turns then use that workspace's context.
answer_formatNoOptional reply format for an agent caller: 'brief' (shortest correct answer, about 150 words), 'decision' (recommendation first, then why, risks and next steps as bullets, about 300 words), or 'full' (the default chat style). Omit for the default. An explicitly requested full document is never cut short.
overflow_consentNoSet true ONLY when the user explicitly asks to continue past their usage limit. On eligible paid accounts (ADP off, non-Essential) over the 4h cap, the turn then runs on the disclosed fallback models up to an additional 2x the plan's token limit. Ignored on free, Essential, ADP, or team-pool accounts and when the overflow bucket is exhausted (fallback_exhausted: true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / message / description
      Added value: +"The question or request, in the user's words. Do not paste framework text."
    • addedInput schema / properties / title / description
      Added value: +"Optional conversation title shown in the ISMS Copilot app."
    • addedInput schema / properties / workspace_id / description
      Added value: +"Optional workspace id (a UUID from list_workspaces) for client or company work; turns then use that workspace's context."
  2. Changed1 schema field changed
    • addedInput schema / properties / assistant
      Added value: +{
+  "description": "Optional assistant for this conversation: 'auto' (default), 'general', or an id from list_assistants. It stays for the whole conversation.",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"Reasoning depth: 'fast' (default), 'think' for deeper reasoning, or 'beyond' for a longer multi-step run (minutes; poll get_reply). think and beyond are not available on every plan; the turn then answers in fast mode."New value: +"Reasoning depth: 'fast' (default), 'think' (paid plans), or 'beyond' (paid plans; agentic multi-step run, minutes-scale, poll get_reply)."
    • changedInput schema / properties / overflow_consent / description
      Previous value: -"Set true only when the user explicitly asks to continue past their usage limit. Where the account allows it, the turn then continues on a faster model; otherwise it is ignored."New value: +"Set true ONLY when the user explicitly asks to continue past their usage limit. On eligible paid accounts (ADP off, non-Essential) over the 4h cap, the turn then runs on the disclosed fallback models up to an additional 2x the plan's token limit. Ignored on free, Essential, ADP, or team-pool accounts and when the overflow bucket is exhausted (fallback_exhausted: true)."
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, it discloses limit/rate behaviour ('reset_at', reset guidance), paid-plan gating for 'think'/'beyond', the daily cap and the beyond_denied_reason fallback, the overflow behaviour on eligible accounts, the 'generating' status requiring a get_reply poll, that a limit error still returns a usable conversation_id, and that docgen_notice must be relayed. It also sets an explicit privacy boundary on what may not be included.

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?

Purpose is front-loaded and almost every sentence carries operational weight, but the text is long and has redundancy: the 'assistant' rule and the 'do not paste framework text' instruction are both restated in the schema descriptions, and the specialist bullet list is verbose. Nothing is misleading, but some compression is possible.

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?

For a 7-parameter, open-world, non-idempotent tool with no output schema, the description covers return shape (conversation_id, message_id, status), the polling path via get_reply, error and limit handling, and account gating. Combined with the schema it leaves nothing an agent needs before calling.

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?

Even at 100% schema coverage, the description adds real meaning: a routing rule for 'assistant' ('a task to do takes the job id even when it names a framework; a question about one framework takes that framework's id; else omit'), plus a per-specialist routing table and a note that the assistant persists for the conversation. It also explains 'beyond' versus 'think' beyond what the enum alone conveys.

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 ('Ask the ISMS Copilot GRC specialist and start a new conversation for one deliverable') and explicitly scopes it to a single deliverable, which separates it from send_message for follow-ups. The framing is unambiguous about what is being created and what it is for.

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?

Gives a dense when-to-use list (clause questions, policy drafting, gap analysis, SoA justifications, incident response, etc.) plus explicit when-not-to-use conditions: code, git, files, questions with no compliance angle, and follow-ups on the same deliverable. It also names the alternative (send_message) for the follow-up case and tells the caller not to paste framework text.

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

All ISMS Copilot 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