Skip to main content
Glama
KyaniteLabs

checkyourself

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Rank Backlog

backlog
Read-onlyIdempotent

Normalize scan findings into a prioritized remediation backlog sorted by severity, category, and ID, with fix summaries and verification steps. Recommends work only; does not modify files.

Instructions

Normalize inline findings and return the complete remediation backlog sorted by severity, category, and finding ID. The highest_severity_batch is a deterministic severity slice; safety and dependency analysis are not performed. Each item includes fix summary, order rationale, verification, rollback idea, learning value, and status. This recommends work only; it does not modify files or mark findings resolved. Requires no authentication. It reads local inputs only, does not make network calls, does not modify local files, and has no external rate limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
findingsYesScan result object, CheckYourself report object, object with findings/remediation_backlog, or a plain list of finding objects to convert into a remediation backlog.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / findings / description
      Added value: +"Scan result object, CheckYourself report object, object with findings/remediation_backlog, or a plain list of finding objects to convert into a remediation backlog."
    • changedInput schema / properties / findings / type
      Previous value: -"object"New value: +[
+  "object",
+  "array"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Backlog result using schema checkyourself-backlog/1.",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds meaningful details: no file modifications, no marking resolved, no authentication, no network calls, and no external rate limits.

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 description is mostly efficient and front-loaded, though a couple of phrases overlap slightly ('recommends work only' and 'does not modify files'). Overall, every sentence adds useful context.

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?

The description covers inputs, output item fields, sorting behavior, determinism, side-effect guarantees, and environmental constraints, making it complete enough even without a detailed output schema.

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

Parameters5/5

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

The single parameter has 100% schema coverage, and the description enriches it by enumerating the accepted input forms: scan result object, CheckYourself report object, object with findings/remediation_backlog, or plain list.

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?

Description states a specific action (normalize and return) on a specific resource (remediation backlog) with clear sorting criteria, distinguishing it from sibling tools like scan or score.

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 usage by describing what the tool does and its limitations, but it does not explicitly name sibling alternatives or provide when-to-use versus when-not-to-use guidance.

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