Skip to main content
Glama
rampify-dev

Rampify MCP Server

link_commit

Link a git commit SHA to a feature spec and optionally a task. Creates full traceability from code to commit to task to spec.

Instructions

Link a git commit SHA to a feature spec and optionally a task. Creates full traceability: code -> commit -> task -> spec.

Deterministic workflow for AI agents:

  1. Retrieve spec via get_feature_spec (spec_id is now in context)

  2. Implement changes and commit code

  3. Run git rev-parse HEAD to capture the exact SHA

  4. Run git remote get-url origin and normalize SSH URLs to HTTPS

  5. Call this tool with the SHA, repo_url, and spec_id (and task_id if applicable)

The commit is recorded in the spec's related_commits array and commit_count is incremented. If task_id is provided, the commit is also linked to the task with a last_commit_at timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoSite domain (e.g., "example.com"). Uses SEO_CLIENT_DOMAIN env var if not provided.
project_idNoProject UUID — use instead of domain when no domain is configured.
spec_idYesUUID of the feature spec to link the commit to (required)
task_idNoUUID of the specific task to link the commit to. If provided, the commit is linked to both the task and its parent spec.
commit_shaYesGit commit SHA to link (from `git rev-parse HEAD` after committing)
repo_urlNoRepository HTTPS URL (e.g., "https://github.com/owner/repo"). Derive from `git remote get-url origin` and normalize SSH to HTTPS.
Behavior5/5

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

No annotations provided, but the description fully discloses side effects: the commit is recorded in the spec's related_commits array, commit_count incremented, and if task_id given, linked with last_commit_at. It also notes URL normalization from SSH to HTTPS.

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?

The description is somewhat long but well-structured with a clear opening, a numbered workflow, and detailed side effects. Each sentence adds useful information, though minor redundancy exists.

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?

Given no output schema and 6 parameters, the description covers the process, parameter derivation, and behavioral effects. It could mention the return value but is otherwise complete and self-contained.

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 is 100% with adequate parameter descriptions. The tool description adds value by explaining how to obtain commit_sha and repo_url (steps 3-4) and clarifying the domain/project_id distinction, going beyond the schema.

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 that the tool links a git commit SHA to a feature spec and optionally a task, creating traceability. This is a specific verb+resource combination and is distinct from all sibling tools.

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 provides a deterministic 5-step workflow for AI agents, including prerequisites like retrieving the spec, committing code, and capturing the SHA. It explains when to use (after commit) and optional task linking, with no ambiguity.

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/rampify-dev/rampify-mcp'

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