Skip to main content
Glama
valentil

FeatureBoard MCP Server

by valentil

Reconcile logged vs git churn

churn_reconcile
Read-only

Reconcile logged additions/deletions with actual git commits to detect drift in churn reporting per ticket.

Instructions

For Done tickets with tagged commits, compare the additions/deletions logged in the work log against the git-actual numstat of their commits. Git-actual comes from recorded commit events (FBMCPF-188) or, failing that, a live git log --grep + numstat cached by hash. Reports per-ticket loggedAdd/loggedDel vs gitAdd/gitDel with a drift ratio (worst first), plus an overall churnAccuracy also surfaced on get_health. Paginated (FBMCPB-42): returns the worst-drift page by default (limit/offset, mirroring list_tasks) so a big board stays inside the token budget — the totals/churnAccuracy rollup is always over ALL reconciled tickets. Pass driftThreshold to omit tickets whose drift ratio is below it, or full:true for every row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fullNoReturn every reconciled ticket (ignores limit/offset) — may be large.
limitNoMax tickets in the returned page (default 25, worst drift first).
offsetNoPage offset into the worst-first list.
projectYes
driftThresholdNoOnly return tickets with driftRatio >= this (e.g. 0.2). Totals still cover all tickets.
Behavior5/5

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

Discloses that it uses cached git log/numstat, pagination with worst-drift first, and that totals cover all tickets. Annotations (readOnlyHint=true) are consistent. No contradictions.

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

Conciseness4/5

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

Packed with information but not overly verbose. Each sentence adds unique value. Could be slightly better structured with bullet points, but efficient overall.

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?

Despite no output schema, the description explains the return format (per-ticket drift, overall churnAccuracy) and pagination semantics. Complete for a reconciliation tool.

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?

Adds value beyond schema: explains limit/offset mirror list_tasks, driftThreshold filters but totals still cover all, full ignores pagination. Schema covers 80% of parameters; description compensates for the missing project description.

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 clearly states it compares work log and git-actual numstat for Done tickets with tagged commits, reporting per-ticket and overall churn accuracy. This is specific and distinguishes from any sibling tool.

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?

Provides context on when to use (Done tickets with tagged commits), pagination behavior (limit/offset, full flag), and drift threshold filtering. However, it does not explicitly exclude alternative tools or provide when-not-to-use guidance.

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

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/valentil/featureboard-mcp'

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