Skip to main content
Glama

Error Fingerprints

empreintes_erreurs

Empreintes d’erreurs : normalise un extrait de logs applicatifs (identifiants variables masqués, secrets expurgés), regroupe les traces équivalentes en signatures de fréquence et compte les occurrences. Deux traces ne différant que par un identifiant produisent une signature de fréquence deux.

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": {
      "traces": "<traces>"
    },
    "name": "empreintes_erreurs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tracesYesExtraits de logs applicatifs à regrouper.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers real behavioral detail: identifiers are masked, secrets are expunged (a privacy-relevant side effect), traces are normalized before comparison, and the return value is signatures plus occurrence counts. It stops short of disclosing limits (1000 traces / 16384 chars per string), ordering of results, or cost, which matters for a batching tool.

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?

Three sentences, front-loaded with the labeled purpose, then the processing pipeline, then one concrete illustrative example. No filler, no repetition of the tool name as content, and the example is the single most useful sentence for predicting behavior.

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 one-parameter tool with no output schema, the description supplies the essential missing piece: the shape of the result (frequency signatures with occurrence counts). It omits ordering, whether signatures are returned as strings or structured objects, and volume limits, which an agent calling with up to 1000 traces would want to know.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns an increment by explaining what happens to the input: entries are normalized, variable identifiers masked, and secrets stripped before grouping. That tells an agent the input is raw logs rather than pre-cleaned strings, which the schema's 'Extraits de logs applicatifs à regrouper' only hints at.

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?

States a specific verb chain and resource: normalizes application log extracts, masks variable identifiers, redacts secrets, groups equivalent traces into frequency signatures, and counts occurrences. No siblings exist, and the description still makes the transformation fully concrete with a worked example ('two traces differing only by an identifier produce a signature of frequency two').

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 implied by the transformation described (feed in raw log extracts, get grouped frequency signatures), but there is no explicit statement of when to reach for this tool, no prerequisites, and no mention of what it is not suited for (e.g., single-trace inspection or non-log text). With no siblings listed, the missing guidance is understandable but still leaves selection to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources