Skip to main content
Glama

get_compliance_score

Calculate an organization's compliance score (0–100) for a regulatory framework, using weighted control statuses to exclude non-applicable controls and reveal gaps.

Instructions

Return the organisation's compliance score (0–100) for a framework.

Score is the weighted average of applicable controls: compliant=1.0, partial=0.5, non_compliant=0.0. Controls marked not_applicable are excluded from the denominator so they do not penalise the score.

Use list_compliance_controls to see per-article breakdown and identify gaps.

Args: framework: Regulatory framework key (optional — omit for aggregate across all).

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_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it discloses the weighted-average formula, the 1.0/0.5/0.0 control values, and the important rule that not_applicable controls are excluded from the denominator so they don't penalise the score. It does not state permission requirements or whether the result is cached/live, which keeps it below 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?

Front-loaded with the return value and range, followed by the scoring rule and the sibling routing hint. No filler sentences; every line (formula, not_applicable exclusion, alternative tool) adds decision-relevant information.

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 no annotations and no output schema, the description still defines the returned value precisely (0–100 weighted score) and its computation, which is the key completeness requirement here. The remaining gap is the set of accepted framework keys, which an agent would need to call this reliably.

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 description coverage is 0%, so the description must compensate: it explains that framework is optional and that omitting it yields an aggregate across all frameworks, which is real meaning beyond the bare string type. However, it never lists valid framework keys or their format, leaving the agent without the value space needed to supply the parameter confidently.

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 ('Return the organisation's compliance score') with explicit scope ('for a framework') and range (0–100). It is clearly distinguishable from the sibling list_compliance_controls, which is named as the per-article alternative.

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 clear routing: use this for the aggregate score, use list_compliance_controls for per-article breakdown and gap identification. Also explains the omit-framework case. It stops short of explicit when-not conditions or naming get_compliance_report as an alternative, but the primary split is stated.

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

Deploy Server

Other Tools