Skip to main content
Glama
Sign In
statica-mcp

statica-mcp

Official
by SuresoftTechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Register project and run first analysis

statica_bootstrap_finish
Destructive

Finalizes project connection by rechecking capture, registering the server project, marking the workspace ready, and running/uploading full analysis; deletes bootstrap backups only after success.

Instructions

Last step of connecting a project: re-check the capture, create the server project, mark the workspace ready, then run the full analysis and UPLOAD it (fullAnalysis). Deletes the backups taken by statica_bootstrap_guard once it succeeds. Covered by the user's approval of the connection; no separate upload question. stage=project means only server registration failed: fix the cause and call again, do not abort. Do not run pre-analyze afterwards. Pass on buildCommandWarning verbatim.

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_bootstrap_finish"
  }
}

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

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description explains exactly why: it deletes the backups taken by statica_bootstrap_guard once it succeeds, and it uploads analysis results. It further discloses authorization context ('covered by the user's approval of the connection; no separate upload question') and the partial-failure semantics of stage=project — context that annotations alone cannot convey.

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 tool's role in the workflow, then the side effects, then the failure and sequencing rules — each sentence carries distinct operational value with no filler. The phrasing is telegraphic and a few clauses (stage=project, buildCommandWarning) assume prior context, which slightly reduces immediate readability.

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 destructive, multi-step, non-idempotent tool with no output schema, the description covers side effects, authorization, retry behavior, and ordering constraints. The only remaining gap is the shape of the return value and what fullAnalysis produces, which the agent must infer from other tools.

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% for the single projectDir parameter, so the schema already carries its meaning and the description adds nothing about it. The mention of 'stage=project' and 'buildCommandWarning' refers to state from other calls rather than to this tool's input, so it does not enrich parameter semantics.

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 concrete multi-step verb sequence (re-check capture, create server project, mark workspace ready, run analysis, upload) for a specific resource (the project). It also distinguishes itself from siblings by naming statica_bootstrap_guard (whose backups it consumes) and by explicitly ruling out statica_pre_analyze afterwards.

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?

Positions itself precisely as the 'last step of connecting a project' and gives an explicit when-not: 'Do not run pre-analyze afterwards.' It also gives a recovery rule for the stage=project failure case (fix the cause and call again, do not abort) and clarifies no separate upload confirmation is needed.

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