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

sphior-code-mcp

by Toraastrta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_findings

Retrieve security vulnerabilities and CVEs across GitHub repositories, with filters for severity and triage status, to review open or resolved code findings.

Instructions

List security vulnerabilities (SAST + SCA) detected by SPHIOR CODE across the user's GitHub repositories. Use this when the user asks about security issues, vulnerabilities, or CVEs in their code. Returns up to 100 findings ordered by detection date (newest first).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of results (1-100). Default: 20
statusNoFilter by triage status. Default: open
severityNoFilter by severity level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden; 'List' implies a read operation, while the text adds concrete scope, a 100-finding cap, and newest-first ordering by detection date. It does not clarify access requirements, pagination or truncation when more findings exist, or the representation of each finding.

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 compact sentences front-load the operation and scope, then provide the usage trigger and result limits and ordering. Every sentence contributes useful selection or invocation information without repetition or filler.

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 list operation with three optional, fully documented parameters, the description supplies nearly everything needed to select and invoke it: coverage, repository scope, trigger, cap, and ordering. Explicit sibling routing and clarification of behavior beyond the 100-finding cap would make it more complete, particularly since no output schema is supplied.

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%, including filter enums and defaults, so the baseline of 3 applies. The statement that the tool returns up to 100 findings largely restates the limit constraint and adds no further semantics for status, severity, or interactions among filters.

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 uses a specific verb and resource, identifies SAST and SCA findings detected by SPHIOR CODE, and scopes them to the user's GitHub repositories. Listing findings across repositories gives some separation from detail or summary siblings, but it does not explicitly distinguish those alternatives.

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 gives a clear usage trigger: requests about security issues, vulnerabilities, or CVEs in the user's code. It does not explain when to prefer siblings such as get_finding for one finding or get_security_summary for an aggregate view.

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