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

sphior-code-mcp

by Toraastrta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_finding

Retrieve complete details for a specific security finding by ID, including CVSS score, CWE, file path, line number, message, and fix hint. Use it to investigate an issue from a findings list.

Instructions

Fetch full details of a single security finding by ID — includes CVSS score, CWE classification, exact file path and line number, vulnerability message, and fix hint. Use when the user wants to investigate a specific issue from list_findings.

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": "get_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
findingIdYesFinding UUID — obtain via list_findings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Fetch' implies a read-only lookup and the field list tells the agent what comes back, but it says nothing about behavior on an unknown ID, permission requirements, or whether the result is cached/live.

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?

Two sentences, zero filler: the capability and its return payload come first, the usage trigger second. Every clause earns its place.

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?

With no output schema, the description usefully enumerates the returned fields, which is the main thing an agent needs to decide whether to call it. Only the error/not-found behavior is left unaddressed for this simple one-parameter read tool.

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% and the single findingId parameter is already documented as a UUID obtainable via list_findings. The description adds only the 'by ID' framing, so the schema does the heavy lifting and 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 ('Fetch full details of a single security finding by ID') and enumerates the returned fields (CVSS, CWE, file path/line, message, fix hint), which clearly separates it from the list-oriented sibling.

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?

Explicitly says to use it 'when the user wants to investigate a specific issue from list_findings', giving a clear trigger and naming the sibling that precedes it. It stops short of stating when not to use it (e.g., bulk retrieval or already-resolved findings), so it is strong but not exhaustive.

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