Skip to main content
Glama

driftguard_health_score

Calculates a 0–100 workspace health score by checking exposed secrets, zombie processes, token budget, and checkpoint readiness.

Instructions

Calcola lo Score di Salute complessivo (0-100) del workspace: verifica segreti esposti, processi zombie, budget token e checkpoint pronti.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It discloses the scoring range (0-100) and the four inspection targets, which implies a read-only aggregate analysis, but it never states that it is side-effect free, how expensive/slow a full sweep is, or whether it triggers any of the underlying checks live.

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 that front-loads the output (the 0-100 health score) and then lists the evidence it is derived from. No filler, no redundancy.

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?

There is no output schema and no annotations, so the description is the only source of truth. It says the result is a 0-100 score but not whether the response includes per-dimension breakdowns, thresholds, or recommendations — a meaningful gap for an aggregate diagnostic tool. The Italian-language description amid English tool names is also a minor accessibility wrinkle.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 applies. The description correctly spends no words on inputs.

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?

Names a specific verb+resource ('Calcola lo Score di Salute complessivo (0-100) del workspace') and enumerates the four dimensions it aggregates (segreti esposti, processi zombie, budget token, checkpoint pronti). The enumeration implicitly distinguishes it from single-concern siblings like driftguard_scan_secrets or driftguard_budget_status, though it never names them explicitly.

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 only implied: the aggregate nature suggests 'call this for an overview first', but there is no explicit when-to-use, when-not, or statement of relationship to the granular sibling checks. An agent must infer that this is a roll-up rather than a replacement for the individual scanners.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.