Skip to main content
Glama
Sign In
statica-mcp

statica-mcp

Official
by SuresoftTechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Show automatic report settings

statica_report_generator_show
Read-only

Shows whether report generation is enabled after each analysis and lists the output formats and report kinds, without changing any settings.

Instructions

Show whether the server generates a report after each analysis, and in which format and kinds. Changes nothing.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "statica_report_generator_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path of the project directory being analyzed (usually the session's working directory).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and 'Changes nothing' largely restates that. The useful additions are what the response reports (enabled state, format, kinds), but the openWorldHint=true annotation is left unexplained for what otherwise looks like a local settings read.

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?

One front-loaded sentence with the scope, the returned fields, and the non-mutating guarantee; no filler or redundancy.

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 one-parameter read tool with full schema coverage and readOnlyHint, this is close to complete: it says what is inspected and that nothing changes. The only shortfall is not explaining the openWorldHint flag or how the settings are surfaced.

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?

The single projectDir parameter has 100% schema description coverage, so the schema already carries the semantics. 'After each analysis' weakly contextualizes the project scope but adds no format or validity detail beyond the schema.

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?

The description gives a concrete verb and resource: it shows whether automatic report generation is enabled and what format/kinds are configured. 'Changes nothing' contrasts it with its mutating sibling statica_report_generator_set, though that sibling is never named.

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?

Usage is only implied: the read-only framing ('Changes nothing') suggests checking the setting before calling statica_report_generator_set, but the description never states when to use this versus that tool explicitly.

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