Skip to main content
Glama

Get security remediations

get_security_remediations
Read-only

Read the Security Center's fix runs: each is one fix Ankra is driving for a finding, with the application and repository, the pull request it opened, its status and reason, attempts, the pipeline run building it, and whether the fix was verified or merged. Without run_id it lists runs newest first, optionally for one finding_id or one application_id; with run_id it returns that run with its event trail. Use it to answer whether a finding is being fixed and where the fix stands. An empty list means no fix run was started, not that the finding is fixed. Read-only; needs security.read. It starts and cancels nothing.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRuns to list, 1 to 100 (default 25).
run_idNoOne run to read with its events.
finding_idNoOnly runs for this finding (from list_security_findings).
application_idNoOnly runs for this application.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation it discloses the required scope (security.read), states 'It starts and cancels nothing,' and gives ordering ('newest first') and a critical interpretation caveat that an empty list means no fix run was started, not that the finding is fixed. Those are exactly the behavioral facts an agent cannot infer from annotations or schema.

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?

The return contents are front-loaded and the mode logic follows in a single tight sentence per idea, with no filler. The field enumeration is dense but each item (pull request, status, attempts, pipeline run, verification) tells the agent something it would otherwise have to discover.

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

Completeness5/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 carries the return-shape burden and does so fully — listing record contents, ordering, event trail for single reads, and the empty-result meaning. Nothing needed to call or interpret this read-only, four-parameter tool is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine semantics: the tool switches between list and single-record mode based on run_id, filters are optional and scoped to one finding or one application, and run_id results include the event trail. That is more than the schema's per-field text conveys.

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?

The definition opens with a specific verb and resource ('Read the Security Center's fix runs') and immediately defines what a run is and what fields it carries, so an agent can distinguish it from finding-level siblings like get_security_finding.

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 states the question this tool answers ('whether a finding is being fixed and where the fix stands') and explains the two modes — list without run_id versus single run with run_id — plus the optional single-finding/application filters. It stops short of naming an explicit alternative tool to prefer for adjacent questions, so it is clear context rather than full routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.