Skip to main content
Glama
putervision

state-memory-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_analytics

Read-onlyIdempotent

Compute workflow metrics, velocity, burndown, cognitive load, decision trails, and contradiction audits to track progress, ROI, and decision conflicts.

Instructions

Compute workflow metrics, velocity, burndown, cognitive load, decision lineages, and contradiction audits (actions: summary, velocity, burndown, value_metrics, cognitive_load, critical_path, context_snapshot, active_context, decision_trail, find_related_decisions, contradictions). Use get_analytics instead of query_graph when calculating high-level progress statistics, ROI metrics, or auditing decision conflicts.

Returns summary dashboard, velocity charts, burndown series, cognitive load metrics, critical path DAG, or contradiction reports.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoNumber of historical days for burndown (default: 14).
actionYesThe analytics or decision analysis action to execute: summary, velocity, burndown, value_metrics, cognitive_load, critical_path, context_snapshot, active_context, decision_trail, find_related_decisions, contradictions.
node_idNoDecision node ID for decision_trail.
projectNoTarget project name or slug.
artifact_idNoArtifact node ID for find_related_decisions.
window_daysNoNumber of days to analyze for velocity (default: 14).
milestone_idNoMilestone ID for critical_path calculation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.1
    • changedInput schema / properties / action / description
      Previous value: -"The analytics or decision analysis action to execute."New value: +"The analytics or decision analysis action to execute: summary, velocity, burndown, value_metrics, cognitive_load, critical_path, context_snapshot, active_context, decision_trail, find_related_decisions, contradictions."
    • addedInput schema / properties / action / enum
      Added value: +[
+  "summary",
+  "velocity",
+  "burndown",
+  "value_metrics",
+  "cognitive_load",
+  "critical_path",
+  "context_snapshot",
+  "active_context",
+  "decision_trail",
+  "find_related_decisions",
+  "contradictions"
+]
  2. Changed3 schema fields changedv1.2.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -true
    • addedInput schema / required
      Added value: +[
+  "action"
+]
  3. Addedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful value by listing the shape of returned artifacts (dashboard, velocity charts, burndown series, DAG, reports) despite no output schema existing, though it does not disclose per-action behavior nuances.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The routing rule is well front-loaded, but the eleven-action list is repeated twice within the description itself and again in the schema, which is redundant. It is somewhat over-sized for the information conveyed.

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?

With no output schema, the description usefully summarizes the return values, and annotations cover the safety contract. It is close to complete for a multi-action tool, missing only action-level guidance about which parameters apply to which action.

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 description coverage is 100% and the enum plus per-parameter descriptions fully document the inputs, so the schema carries the burden. The description restates the action list but adds no syntax, defaults, or format detail beyond what the schema already provides.

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?

The description gives a specific verb+resource ('Compute workflow metrics') and enumerates the concrete analytics it produces, so an agent knows exactly what this tool does. It also explicitly distinguishes itself from the similarly-named sibling query_graph.

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?

It names the alternative (query_graph) and the conditions that select this tool (high-level progress statistics, ROI metrics, decision-conflict auditing). However, the routing guidance only covers the metrics/high-level cases and does not explain when to pick the decision-analysis actions (decision_trail, find_related_decisions, context_snapshot) over other siblings.

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