Skip to main content
Glama

get_remediation_impact

Read-onlyIdempotent

Summarise the pull requests the Plutus GitHub App opened for this account from savings recommendations (automated fixes) in a window, default the last 90 days, at most 365: how many were opened, merged, closed without merging by the team, closed by Plutus itself (withdrawn, superseded or replaced, not a rejection) and are still open (each counted once, in its current state), how many were opened automatically versus requested by an admin, the median hours from opening to merge, a per-month series by the month each was opened, the change kinds, and the 10 most recent (number, GitHub URL, state, dates, estimated saving). Plutus never merges a pull request: a person on the account does. Every money figure is an estimate, in USD cents (the response's currency): the savings recommendation's estimated monthly saving as it stood when the pull request opened, a potential monthly saving once the change is applied. A merged change saves nothing until it is applied (for example by a Terraform apply). After a merge Plutus checks the resource inventory and gives each merged change a verification verdict: confirmed (the resource now shows the new configuration), pending (too early to tell), not_applied (merged, still the old configuration after 21 days) or unverifiable (the resource is gone, was never inventoried, or no evidence can be read). pull_requests.verification counts merged changes by verdict, estimated_monthly_savings.merged_by_verification splits the merged total by verdict (it adds up to merged_cents), and each recent merged pull request has verification.status. Confirmed means the change is in place, not that the saving was measured: the amount is still the estimate. Never call it realised, verified or guaranteed saving. Each recommendation is priced once per total; merged_priced/open_priced say how many pull requests the totals cover; a null total means none was priced, not zero. Jobs that never opened a pull request are not counted. available false means automated fixes are not offered to this account. Mirrors GET /api/accounts/:accountId/remediation/impact.

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_remediation_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow length in days, ending now (default 90)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare the read-only, idempotent, non-destructive profile, and the description goes well beyond them: Plutus never merges PRs, all money figures are estimates in USD cents, a merged change saves nothing until applied, verification verdicts (confirmed/pending/not_applied/unverifiable) with the 21-day rule, per-recommendation pricing counted once, and null totals meaning 'none priced' rather than zero. It also constrains downstream phrasing ('never call it realised, verified or guaranteed saving'), which is genuine behavioural context an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key purpose is front-loaded and every clause is substantive, but the description is a single extremely dense run-on spanning counting rules, pricing caveats, verification logic and phrasing prohibitions, which harms scannability. Some material (such as the repeated emphasis that figures are estimates, and the mirroring of the REST endpoint) could be compressed or trimmed without loss.

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 full burden of explaining the response shape and does so: it names the fields agents will encounter (pull_requests.verification, estimated_monthly_savings.merged_by_verification, merged_priced/open_priced, currency, the recent-PR fields) and explains the counting and null semantics behind them. Nothing essential for correct interpretation of a read-only report tool appears missing.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents the 'days' window, its default of 90 and its 365 ceiling. The description's restatement of the same default and cap adds no meaning beyond the structured field, so the baseline of 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?

The opening sentence gives a specific verb and resource — summarising pull requests the Plutus GitHub App opened from savings recommendations — and enumerates exactly which measures are returned (counts by state, automatic vs admin-requested, median hours to merge, per-month series, change kinds, 10 most recent). This is far more than a restatement of 'get remediation impact' and lets an agent recognise the tool without opening the schema.

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 implied by the content: this is the tool that reports outcomes of automated fix pull requests, and 'available false means automated fixes are not offered to this account' signals a precondition. However, it never states when to prefer this over list_savings_recommendations or other siblings, and gives no explicit when-not guidance, leaving selection to inference from the name and content.

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.

Resources