projectpulse-mcp

get_dora_metrics

Read-onlyIdempotent

Calculate DORA metrics (deployment frequency, lead time, change failure rate, MTTR) for a GitHub repository to evaluate team delivery performance over a chosen period.

Instructions

Calculates DORA proxy metrics (deployment frequency, lead time, change failure rate, MTTR) for a GitHub repository.

Side effects: None. This is a strictly read-only operation.
Data sources: GitHub REST API (releases, actions/runs, pulls).
Auth requirements: No special authentication required for public repositories. Private repositories require GITHUB_TOKEN.
Rate limits: Subject to standard GitHub API limits. Heavy API usage due to multiple list endpoints being queried.
Return shape: Returns a JSON object with calculated DORA metrics over the specified period.
Usage guidelines: Use this tool ONLY to evaluate DORA metrics and team delivery performance. DO NOT use this tool for other checks:
- For raw workflow statuses, use 'check_ci_status' instead.
- For a computed A-F health score grading, use 'get_health_score' instead.
- For general repository metadata, use 'get_repo_health' instead.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No	Number of past days to analyze (default: 30)
`repo`	Yes	GitHub repository name (e.g., 'sdk')
`owner`	Yes	GitHub repository owner (e.g., 'modelcontextprotocol')

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mttr`	Yes
`repo`	Yes
`owner`	Yes
`lead_time`	Yes
`measured_to`	Yes
`period_days`	Yes
`measured_from`	Yes
`change_failure_rate`	Yes
`deployment_frequency`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedv1.1.7Sep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "change_failure_rate": {
+      "additionalProperties": false,
+      "properties": {
+        "failed_runs": {
+          "type": "number"
+        },
+        "rate_percent": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "total_runs": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "total_runs",
+        "failed_runs",
+        "rate_percent"
+      ],
+      "type": "object"
+    },
+    "deployment_frequency": {
+      "additionalProperties": false,
+      "properties": {
+        "per_week": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "releases_count": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "releases_count",
+        "per_week"
+      ],
+      "type": "object"
+    },
+    "lead_time": {
+      "additionalProperties": false,
+      "properties": {
+        "median_hours": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "pr_count": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "median_hours",
+        "pr_count"
+      ],
+      "type": "object"
+    },
+    "measured_from": {
+      "type": "string"
+    },
+    "measured_to": {
+      "type": "string"
+    },
+    "mttr": {
+      "additionalProperties": false,
+      "properties": {
+        "incidents_count": {
+          "type": "number"
+        },
+        "median_hours": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "median_hours",
+        "incidents_count"
+      ],
+      "type": "object"
+    },
+    "owner": {
+      "type": "string"
+    },
+    "period_days": {
+      "type": "number"
+    },
+    "repo": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "owner",
+    "repo",
+    "period_days",
+    "measured_from",
+    "measured_to",
+    "deployment_frequency",
+    "lead_time",
+    "change_failure_rate",
+    "mttr"
+  ],
+  "type": "object"
+}

Addedv1.1.4Sep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description adds concrete behavioral detail: no side effects, GitHub REST API data sources, public vs. private auth requirements, standard API rate limits, and heavy multi-endpoint API usage. This is exactly the kind of context that helps the agent predict cost and failure modes.

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 uses compact bullet points with the core purpose first, followed by behavior, constraints, return shape, and usage routing. Each section adds distinct information; the only mild redundancy is 'Side effects: None' alongside 'strictly read-only,' but this does not meaningfully bloat the definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

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

For a moderately complex metrics tool with an output schema, the description covers purpose, exclusions, auth, rate limits, data sources, side effects, and return shape. Combined with the fully described input schema and annotations, there are no significant gaps an agent would need to guess about.

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 each property (days, repo, owner) already has a clear schema description with defaults and examples. The tool description does not add parameter-specific detail, but with full schema coverage it has no obligation to; baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Calculates DORA proxy metrics (deployment frequency, lead time, change failure rate, MTTR) for a GitHub repository.' It names the exact metrics and scope, and the usage-guidelines section explicitly separates it from sibling tools, so an agent can distinguish it immediately.

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

Usage Guidelines5/5

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

The description gives unambiguous when-to-use guidance: 'Use this tool ONLY to evaluate DORA metrics and team delivery performance.' It also provides explicit not-this-tool routing for check_ci_status, get_health_score, and get_repo_health, making the selection decision clear without requiring the agent to infer.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexbypa/github-projectpulse-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server