Skip to main content
Glama
Sign In
Latent Defense MCP Server

Latent Defense MCP Server

Official
by latent-defense
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

triage_stats

Retrieve triage statistics for security findings, grouped by status, severity, and repository, to assess prioritization and track progress.

Instructions

Get triage statistics (counts by status, severity, repository).

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

Input Schema

NameRequiredDescriptionDefault
repository_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. The description only mentions counts by categories, implying read-only aggregation, but lacks details on performance, auth requirements, scope (all repositories vs filtered), or pagination. Minimal transparency.

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?

A single sentence of 12 words, front-loaded with the core action. No redundant information. 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.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple nature (one optional parameter, output schema exists), the description covers the basic functionality. However, it lacks usage context and behavioral details, making it adequate but not fully complete for an agent to use without additional inference.

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 coverage is 0%, so the description must compensate. The description explains the output groupings (status, severity, repository) which implicitly clarifies the role of the 'repository_id' parameter (filtering by repository). This adds meaning beyond the empty schema, but does not explicitly describe the parameter format or behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets triage statistics with groupings by status, severity, and repository. The verb 'Get' and resource 'triage statistics' are specific, and the groupings differentiate it from generic stats tools. However, it does not explicitly distinguish from sibling stats tools like 'ticket_stats' or 'infra_stats'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it. With sibling tools for different statistics types, explicit usage guidelines would help the agent decide.

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