Skip to main content
Glama
Sign In
sphior-code-mcp

sphior-code-mcp

by Toraastrta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resolve_finding

Mark a vulnerability finding as resolved after a fix has been applied, optionally recording a reason. Track remediation status so only genuinely remediated issues are closed.

Instructions

Mark a finding as resolved (e.g., after applying a fix). Use only when the vulnerability has actually been remediated. For false positives, use mark_false_positive instead.

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": {
      "findingId": "<findingId>"
    },
    "name": "resolve_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional reason for closing
findingIdYesFinding UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it discloses the state change (finding becomes resolved) and the semantic precondition, which is real value. It does not state whether the resolution is reversible, what permissions or role are required, whether a reason is retained in an audit trail, or what the call returns. For an irreversible-looking mutation these gaps keep it at a middling score.

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 short sentences, each carrying distinct load: the action, the precondition, and the alternative routing. The action and its constraint are front-loaded and nothing is redundant with the title or schema.

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?

A simple two-parameter mutation whose parameters are fully documented by the schema, so the description does not need to restate them. The only unresolved item an agent might want — reversibility or post-resolution state — is unaddressed, and there is no output schema to compensate.

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% — findingId is documented as a Finding UUID and reason as an optional string capped at 500 characters. The description adds no format, default, or validation detail beyond the schema, so the 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 ("Mark a finding as resolved") plus a parenthetical example of the triggering context ("after applying a fix"). It explicitly separates this tool's purpose from the sibling mark_false_positive, so an agent can pick correctly without inspecting schemas.

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?

Gives an explicit precondition ("Use only when the vulnerability has actually been remediated") and names the alternative path for the other case ("For false positives, use mark_false_positive instead"). Both when-to-use and when-not-to-use are stated with the routing target.

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