Rubric Protocol MCP Server

framework_detect

Detects applicable regulatory frameworks—such as EU AI Act, HIPAA, and NIST AI RMF—from decision payloads so you can identify compliance requirements offline without an API key.

Instructions

Auto-detect applicable regulatory frameworks (EU AI Act, SR 26-2, HIPAA, NIST AI RMF, etc.) from decision content. Works offline, no key required.

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": {
      "payload": "<payload>"
    },
    "name": "framework_detect"
  }
}

Input Schema

Name	Required	Description	Default
`payload`	Yes
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.4Nov 9, 2026

TDQS

C2.9/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real operational context: 'works offline, no key required' tells the agent there is no auth or network dependency. It does not disclose the output shape, determinism/confidence of detection, or whether partial input yields empty results, which matters for a detection tool.

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?

Two sentences, front-loaded with the core action and examples, with the offline constraint trailing efficiently. No wasted wording; only the trailing 'etc.' is slightly vague.

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?

No output schema, no annotations, and 0% parameter coverage mean the description is the only source of truth, yet it never says what a detection result looks like (list of framework names? scores? matches?) or how the undocumented 'metadata' affects results. Adequate to identify the tool, insufficient to invoke it confidently.

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

Parameters2/5

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

Schema description coverage is 0% across two parameters, so the description must compensate. 'From decision content' loosely maps to the required 'payload', but the free-form 'metadata' object is entirely unexplained, and there is no guidance on expected payload size, structure, or format.

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?

States a specific verb and resource ('Auto-detect applicable regulatory frameworks') and enumerates concrete examples (EU AI Act, SR 26-2, HIPAA, NIST AI RMF), so an agent knows exactly what it produces. It does not differentiate itself from any sibling (attest, verify, screen_entity, etc.), leaving that to inference.

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

Usage Guidelines2/5

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

The phrase 'from decision content' implies the input context in which it applies, but there is no explicit when-to-use statement, no when-not-to-use, and no mention of any sibling alternative that might be preferred. An agent must guess whether to call this before or after verify/attest.

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

Deploy Server