Skip to main content
Glama
ariekogan

ateam-mcp

by ariekogan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

ateam_github_diff

Compare two branches (default dev vs main) to preview commits and files about to ship, showing ahead_by count for review before promotion.

Instructions

PRE-FLIGHT BEFORE PROMOTE. Compares dev (head) vs main (base) by default — shows exactly which commits and files are about to ship if you call ateam_github_promote() next.

Use this when you want to: • Review changes before promoting to prod • See if dev is ahead of main at all (returns ahead_by: 0 if nothing to promote) • Inspect arbitrary branch/tag/commit comparisons (override base/head)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
solution_idYesThe solution ID
baseNoBase branch/tag/sha (the target — what you're comparing TO). Default: 'main'.main
headNoHead branch/tag/sha (the source — what you're comparing FROM). Default: 'dev'.dev

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.52

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist. Description fully discloses behavior: compares branches, shows commits/files, returns ahead_by. No destructive implications.

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?

Concise 4 sentences with bullet points. Front-loaded purpose, then usage. No fluff.

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?

Adequately describes input, behavior, and output (ahead_by). No output schema but description covers key return info.

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 100% but description adds value by explaining defaults and ability to override for arbitrary comparisons.

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?

Description states specific verb 'compares dev vs main' and links to promote tool. Clearly distinguishes from sibling tools like ateam_github_promote and ateam_github_log.

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 explicit bullet points on when to use (review before promote, check if dev is ahead, arbitrary comparisons). Lacks explicit when-not but context is clear.

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