Skip to main content
Glama
Sign In

Regulane compliance check

by com.regulane
OverviewDiscussionsAdmin

Get Regulane secure-coding rules

get_compliance_rules
Read-only

Returns the workspace's secure-coding rules: what to look for, how to fix it, and the ISO 27001 Annex A controls and DPDP Act sections each rule evidences. Call this before reviewing a change, then report with report_compliance_check.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_compliance_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
areasNoOnly the rules in these areas. Omit for all rules (recommended).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description adds real behavioral context by describing what each returned rule contains (what to look for, how to fix it, control/section mappings). It does not mention workspace-scoping preconditions or result size, so not a 5.

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, zero filler. The return-content summary comes first and the sequencing instruction second, matching the order an agent needs them.

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?

No output schema exists, and the description compensates by describing the shape of each returned rule and the compliance mappings. Combined with the annotations' read-only profile and the fully documented optional filter, an agent has everything needed to call it correctly.

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 single optional 'areas' parameter is fully documented, including the 'omit for all rules (recommended)' default. The description adds no parameter meaning beyond the schema, 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 ('Returns the workspace's secure-coding rules') and then enumerates the payload: detection guidance, remediation guidance, and ISO 27001 Annex A / DPDP Act mappings. It is clearly a rule-catalog fetch, not an assessment, which distinguishes it from report_compliance_check.

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

Usage Guidelines4/5

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

Gives explicit ordering guidance ('Call this before reviewing a change, then report with report_compliance_check'), naming the sibling as the follow-on step. It lacks an explicit when-not-to-call condition, but the workflow context is unambiguous.

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

All Regulane compliance check 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