Skip to main content
Glama
Sign In
keyshade-mcp

keyshade-mcp

Official
by keyshade-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

sync_fork

Synchronizes a forked project with its parent to incorporate upstream changes. Optionally performs a hard sync that replaces all content.

Instructions

Syncs a forked project with its parent

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectSlug": "<projectSlug>"
    },
    "name": "sync_fork"
  }
}

Input Schema

NameRequiredDescriptionDefault
hardSyncNoWhether to perform hard sync (replaces everything)
projectSlugYesForked project slug to sync

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose what 'sync' entails (e.g., direction, merge strategy, overwrite behavior), nor does it explain the hardSync parameter's implications beyond the schema. Behavioral traits like potential data loss or conflict handling are unaddressed.

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?

Single sentence is concise and front-loaded with the core action. No redundant or extraneous information.

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

Completeness2/5

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

For a simple tool with 2 parameters and no output schema, the description is inadequate. It fails to explain the two sync modes (normal vs hard), success/error behavior, or side effects like overwriting local data. More context is needed for effective use.

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 coverage is 100% with parameter descriptions. The tool description adds no additional meaning beyond the schema; it merely repeats the action. Baseline 3 is appropriate since schema already documents parameters, but description adds no extra value.

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 clearly states the action ('Syncs') and the resource ('forked project with its parent'). It distinguishes from sibling tools like fork_project (creates fork) and unlink_fork_parent (removes link), providing a specific verb-resource pair.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like fork_project or unlink_fork_parent. No context about prerequisites or when not to use, leaving the agent without decision support.

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