Skip to main content
Glama

Review Diagram Compliance

flowzap_compliance_check
Read-only

Run an automated SOC2 / GDPR / PIPL / EU AI Act architectural compliance review of a FlowZap Code data flow. Returns a Markdown summary of findings (control · status · detail · recommendation) for each framework whose elements are detectable in the diagram. Free quota: 10 free compliance reviews per client per rolling 30-day period. For unlimited manual reviews, paste your code at https://flowzap.xyz/soc2-gdpr-pipl-compliance-checker. Processor disclosure (GDPR Art. 13): analysis powered by Deepseek (Hangzhou DeepSeek AI, China) — see https://flowzap.xyz/legal/subprocessors. This is an advisory architectural review, not legal advice.

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": {
      "code": "<code>"
    },
    "name": "flowzap_compliance_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
lngNoOutput language for findings. Default: 'en'.
codeYesFlowZap Code to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false), and the description adds substantial context beyond them: the Markdown findings structure (control · status · detail · recommendation), a rolling 30-day quota of 10 calls, and that analysis is sent to a third-party processor (Deepseek, China) with a subprocessor link. It also scopes expectations by stating this is advisory architectural review, not legal advice.

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?

Front-loaded with the core action and output, then quota, then legal disclosure — a sensible ordering. The subprocessor URL and disclaimer add length, but they are compliance-mandated content rather than filler, so the text earns most of its space.

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?

For a two-parameter, read-only analysis tool with no output schema, the description covers return format, cost limits, data-handling, and scope of the advice. The one gap is what happens when the free quota is exhausted (error shape or fallback behavior), which the agent would have to discover at call time.

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 100%, so both parameters are already documented, including the lng enum values and default. The description reinforces that 'code' is a FlowZap Code data flow but adds no format, size, or validation detail 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 — 'Run an automated SOC2 / GDPR / PIPL / EU AI Act architectural compliance review of a FlowZap Code data flow' — and names the output format. This is clearly distinct from siblings like flowzap_validate, flowzap_fix, and flowzap_diff, which handle syntax/correction rather than compliance frameworks.

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

Usage Guidelines3/5

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

It gives one actionable routing hint — use the web page for unlimited manual reviews once the free quota is exhausted — and discloses the 10-per-30-day quota, so the agent can reason about failure modes. However, it never states when to prefer this over flowzap_validate or flowzap_fix, nor any prerequisite about what constitutes valid FlowZap Code input.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.