Skip to main content
Glama
Sign In
gmi-security-mcp

gmi-security-mcp

by Jayanng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_finding

Retrieves a stored security finding by ID, including code, evidence, verdict history, pipeline events, verification results, business impact, and triage memories for review and investigation.

Instructions

Get one stored finding in full: code, evidence, verdict history, pipeline events, verification results, business impact, and matching triage memories.

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": {
      "finding_id": "<finding_id>"
    },
    "name": "get_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
db_pathNo
finding_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.11

TDQS

B3.2/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 behavioral burden. It discloses useful return-content detail (verdict history, pipeline events, triage memories), but says nothing about behavior on a missing/invalid finding_id, whether the call is read-only, or what db_path selects.

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?

A single front-loaded sentence with no filler; the enumerated field list is dense but all of it is substantive. The long list partly duplicates the output schema, but it still helps an agent decide whether this tool returns what it needs.

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

Completeness3/5

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

Since an output schema exists, the description need not explain return values, yet it spends most of its text there. The genuinely missing pieces for a 2-parameter lookup tool are the meaning of db_path and not-found behavior, leaving the definition adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, and the description explains neither. finding_id is only weakly implied by "one stored finding," and db_path is completely undocumented in both the schema and the prose.

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?

States a specific verb and resource ("Get one stored finding in full") and enumerates the payload: code, evidence, verdict history, pipeline events, verification results, business impact, and triage memories. This clearly distinguishes it from list-style siblings, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Usage is only implied by the singular "one stored finding" phrasing and the required finding_id, which suggests fetching a record you already have an ID for. There is no explicit guidance on when to prefer this over list_findings to locate an ID, nor any stated preconditions.

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