Spotter-SAST

Overview Schema Source Related Servers Discussions Admin

compliance_analytics_dashboard

Analyze compliance status over custom time ranges for selected frameworks, with optional predictive insights to identify trends.

Instructions

Generate advanced compliance analytics and insights

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": {
      "time_range": "<time_range>"
    },
    "name": "compliance_analytics_dashboard"
  }
}

Input Schema

Name	Required	Description
`time_range`	Yes	Analysis time range
`frameworks`	No	Specific frameworks to analyze
`include_predictions`	No	Include predictive analytics

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0May 26, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are present, and the description does not disclose behavioral traits such as read-only vs. mutation, required permissions, side effects, or output format. The description is too brief to provide transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence), which is concise but at the cost of necessary detail. It is not structured or informative enough to be effective.

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?

Given the presence of nested parameters, no output schema, and many sibling tools, the description fails to explain what the tool actually does, what output to expect, or how it differs from others like compliance_status_overview. Completeness is low.

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%, so parameters are documented in the schema. The description does not add meaning beyond the parameter names and descriptions, but it does not hurt. Baseline is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Generate advanced compliance analytics and insights' indicates it produces analytical results, but it is generic and does not differentiate from similar tools like compliance_status_overview or security_dashboard. The word 'advanced' is vague.

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?

No guidance is provided on when to use this tool versus sibling tools. There is no mention of prerequisites, limitations, or alternatives. The agent receives no help in deciding context.

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