Skip to main content
Glama
Sign In
viberevert

viberevert

by madeinplutofabio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

classify_risk

Summarize check report findings into per-severity counts (critical, high, medium, low) to deliver a clear risk histogram without requiring thresholds.

Instructions

Project a check report's findings into per-severity counts (critical, high, medium, low). Read-only (class A per D99.V); no threshold input -- returns the full per-level histogram.

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

Input Schema

NameRequiredDescriptionDefault
reportNo
sessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Explicitly states 'Read-only' and 'no threshold input', providing key behavioral context. Since no annotations exist, the description carries the burden and addresses safety and side-effect concerns adequately, though other traits (e.g., performance) are omitted.

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?

Two succinct sentences with no redundancy. The structure flows logically from purpose to behavioral notes, making it easy to parse.

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?

Given no output schema, the description adequately describes the return (per-level histogram) and mentions the lack of threshold filtering. It covers core functionality, though parameter details are missing.

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 has 0% coverage for parameters 'report' and 'session'. The description hints that 'report' is a check report but does not explain 'session' or clarify expected formats, leaving significant ambiguity.

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?

Clear verb+resource: 'Project a check report's findings into per-severity counts' precisely describes the operation and output. Distinct from siblings by its focus on severity histograms.

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?

Implicitly indicates when to use (when severity counts are needed) and mentions 'no threshold input' to clarify scope, but does not explicitly contrast with alternative tools like 'list_risky_files'.

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