Skip to main content
Glama
Sign In
strands-sentinel

strands-sentinel

by Ishant5436
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sentinel_generate_remediation_patch

Generate actionable remediation guidance for a violation reported by an audit tool, including steps to resolve the issue.

Instructions

Return structured remediation guidance for a violation previously reported by an audit tool.

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": {
      "violation_id": "<violation_id>"
    },
    "name": "sentinel_generate_remediation_patch"
  }
}

Input Schema

NameRequiredDescriptionDefault
violation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says the tool 'returns' guidance, which suggests a read-only operation, but it does not disclose whether any state changes occur, whether credentials are needed, or what happens for invalid or unknown violation IDs.

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?

The description is a single, focused sentence with no filler. It front-loads the action and object, and every word contributes to understanding the tool's purpose.

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 one-parameter tool with an output schema, the description is mostly sufficient to guide a call. The main gaps are explicit usage boundaries and behavioral side effects, but these are minor given the tool's low complexity.

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 0%, and there is only one parameter, violation_id. The description adds meaning by tying the parameter to a previously reported audit violation, but it does not clarify the expected format, origin, or how to obtain a valid violation ID.

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 description states a specific verb ('Return'), a specific resource ('structured remediation guidance'), and a clear precondition ('a violation previously reported by an audit tool'). This clearly distinguishes it from sibling tools like sentinel_audit_workspace or sentinel_run_test_suite.

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?

The description implies the tool should be used after an audit tool has reported a violation, which gives useful context. However, it does not explicitly state when not to use it or name alternative tools for related scenarios.

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