Skip to main content
Glama
Sign In
statica-mcp

statica-mcp

Official
by SuresoftTechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Replace project rulesets

statica_ruleset_set
DestructiveIdempotent

Replaces a server project's ruleset selection with the specified IDs and disables all unlisted rulesets. Check the current selection first, then confirm the final list before applying.

Instructions

Replace the server project's ruleset selection. FULL REPLACEMENT: every ruleset not listed is turned off, so call statica_ruleset_show first and build on its current selection. At least one id is required. Applies to everyone using the server project; confirm the final list with the user before calling.

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>",
      "rulesetIds": "<rulesetIds>"
    },
    "name": "statica_ruleset_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path of the project directory being analyzed (usually the session's working directory).
rulesetIdsYesIds of every ruleset that should be on after the call.
localeLanguageNoRule display language such as ko_KR or en_US. Omit to keep the current one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive and idempotent, but the description adds the crucial blast radius: every unlisted ruleset is turned off, and the change applies to everyone using the server project. That shared-impact disclosure and the user-confirmation requirement go well beyond what the annotations convey.

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?

Three tight sentences, front-loaded with the operation and its most dangerous property (full replacement). Every clause carries actionable information; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, shared-state mutation with no output schema, the definition covers scope of impact, prerequisite read, minimum input, and human confirmation. Nothing an agent needs to call it safely is missing.

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 the schema already documents projectDir, rulesetIds, and localeLanguage, including that rulesetIds is the complete desired set. The description reinforces the full-replacement reading of rulesetIds but adds no syntax or format detail beyond the schema; 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 ('Replace the server project's ruleset selection') and immediately clarifies the replacement semantics, which distinguishes it from the read-only statica_ruleset_show. An agent can tell what this does and how it differs from the sibling without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent to statica_ruleset_show first and instructs it to build on the current selection, states a hard prerequisite (at least one id), and adds a confirmation step with the user before calling. When-to-use, prerequisite, and pre-call check are all present.

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