PerfLens MCP Server

by link0-o

Overview Schema Source Related Servers Discussions Admin

Python

Local

analyze_trace_evidence

Idempotent

Deterministically analyze stored sched, off-CPU, and lock trace evidence and verify its integrity before agent use.

Instructions

Deterministically analyze a stored, normalized sched/off-CPU/lock TraceEvidence artifact and verify it before Agent use.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`trace_evidence_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Default
`uri`	Yes
`summary`	Yes
`artifact_id`	Yes
`artifact_type`	Yes
`schema_version`	No	1.0
`evidence_quality`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.3.2Aug 28, 2026

addedOutput schema / $defs / EvidenceQuality / properties / kernel_context_self_percent

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Kernel Context Self Percent"
+}

addedOutput schema / $defs / EvidenceQuality / properties / kernel_context_self_weight

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Kernel Context Self Weight"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unknown_context_self_percent

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unknown Context Self Percent"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unknown_context_self_weight

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unknown Context Self Weight"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unresolved_kernel_self_percent

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unresolved Kernel Self Percent"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unresolved_kernel_self_weight

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unresolved Kernel Self Weight"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unresolved_unknown_context_self_percent

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unresolved Unknown Context Self Percent"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unresolved_unknown_context_self_weight

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unresolved Unknown Context Self Weight"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unresolved_user_self_percent

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unresolved User Self Percent"
+}

addedOutput schema / $defs / EvidenceQuality / properties / unresolved_user_self_weight

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Unresolved User Self Weight"
+}

addedOutput schema / $defs / EvidenceQuality / properties / user_context_self_percent

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "User Context Self Percent"
+}

addedOutput schema / $defs / EvidenceQuality / properties / user_context_self_weight

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "User Context Self Weight"
+}

Addedv0.3.0Aug 21, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already provide idempotentHint=true and destructiveHint=false but readOnlyHint=false. The description adds determinism and the verify-before-use context, which is useful. However, it does not disclose whether verification writes state, requires special permissions, or has other side effects, which matters given readOnlyHint=false.

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?

The description is a single compact sentence that front-loads the action and resource, then adds the verification purpose. Every phrase earns its place: deterministic, stored, normalized, artifact type, and before Agent use.

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 an output schema and idempotent annotation, the description is largely complete: it states the input, the artifact type, and the intended timing. The main missing piece is clarity on side effects given readOnlyHint=false, but the output schema and annotations absorb much of the burden.

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?

With 0% schema description coverage, the description must compensate. It references TraceEvidence artifact, making trace_evidence_id's role mostly inferable as the identifier of that artifact. But it does not explain where the ID comes from, its format, or any validation requirements, leaving a modest gap.

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 uses a specific verb ('analyze') and identifies a precise resource: a stored, normalized sched/off-CPU/lock TraceEvidence artifact. It also adds the intended gate, 'verify it before Agent use.' However, it does not explicitly differentiate from sibling tools like verify_trace_analysis or verify_analysis, which may overlap in purpose.

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

Usage Guidelines4/5

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

The description gives clear usage context: use this tool on a stored, normalized TraceEvidence artifact before Agent consumption. It implies a precondition and timing, but it does not mention alternatives or when-not-to-use conditions, so it stops short of full routing guidance.

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

Deploy Server