Skip to main content
Glama
Sign In
statica-mcp

statica-mcp

Official
by SuresoftTechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Turn automatic analysis on or off

statica_set_auto_analysis
Idempotent

Enable or disable automatic Stop-hook analysis after each response for one project or globally; manual analysis commands keep working.

Instructions

Turn the Stop-hook analysis after each response on or off, for this project or globally. Commands such as statica_pre_analyze keep working either way. Local setting only.

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": {
      "enabled": "<enabled>"
    },
    "name": "statica_set_auto_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
globalNoApply to every project instead of this one.
enabledYestrue to turn automatic analysis on, false to turn it off.
projectDirNoAbsolute path of the project. Required unless global is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the write/idempotent/non-destructive profile, and the description adds genuine behavior context: the setting governs Stop-hook analysis after each response, it does not disable other commands like statica_pre_analyze, and changes are stored locally. It stops short of saying where the setting persists or whether anything else is affected when 'global' is used.

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?

Three short sentences, front-loaded with the action, and the non-interference note about statica_pre_analyze earns its place. The trailing 'Local setting only' is terse to the point of ambiguity — it is unclear whether it qualifies the 'global' option or refers to storage location.

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 simple three-parameter toggle with full schema coverage, strong annotations, and no output schema, the description covers what the switch controls and what it does not break. The only real gap is the unexplained 'Local setting only' phrase, which leaves the agent uncertain about the scope of the global option.

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 all three parameters ('enabled', 'global', 'projectDir') are already documented in the schema. The description only reinforces the project-vs-global distinction in prose; it adds no new meaning about defaults or what happens when 'global' is true and 'projectDir' is omitted (beyond the schema's note).

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 object ('Turn the Stop-hook analysis after each response on or off') plus scope ('for this project or globally'), so the agent knows exactly which setting is toggled. It does not name any sibling it competes with, and the closing phrase 'Local setting only' sits awkwardly next to the 'globally' option.

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?

It conveys the usage context clearly: this is for enabling/disabling automatic post-response analysis rather than running analysis itself, and it explicitly notes 'Commands such as statica_pre_analyze keep working either way,' which tells the agent manual analysis is the alternative and is unaffected. No explicit 'do not use this when...' exclusion is given.

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