Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_github_contribution_setup

Prepare or create a GitHub fork for publishing reviewed AdsMCP changes, with confirmation required before the configured token saves the fork setup.

Instructions

Prepare an optional GitHub fork for publishing reviewed AdsMCP changes. confirm=true may create the fork through the configured GitHub token.

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": {
      "confirm": "<confirm>"
    },
    "name": "ads_github_contribution_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet true only after reviewing the upstream repository and agreeing to create or save the fork setup.
create_forkNoCreate a personal fork through the GitHub API when one is not already configured; defaults to true.
upstream_repositoryNoGitHub owner/repository for the upstream project; defaults to ADSMCP_UPSTREAM_REPOSITORY or the local origin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the tool is optional, that creation is gated behind confirm=true, and that it authenticates via a configured GitHub token (an auth prerequisite). It stops short of stating idempotency, what confirm=false persists, or side effects on existing config.

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?

Two sentences, front-loaded with the purpose and followed by the one behavioral caveat. No filler or redundancy.

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

Completeness3/5

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

A three-parameter mutation tool with no annotations and no output schema needs to say more: what result a caller gets (fork URL, saved configuration), what confirm=false does, and whether the fork is created only when none is configured (that detail lives only in the schema). Adequate but with clear gaps.

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%, so all three parameters are already documented, including defaults for create_fork and upstream_repository. The description only restates the confirm=true → fork creation link, adding little syntax or behavior beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: prepare an optional GitHub fork for publishing reviewed AdsMCP changes. It is clearly distinguishable from status/create_pr siblings by naming the fork-setup action, though it never explicitly contrasts with ads_github_contribution_status or ads_github_contribution_create_pr.

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

Usage Guidelines3/5

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

"Optional" and "confirm=true may create the fork" imply this is a preparatory step used before publishing contributions, but there is no explicit when-to-use/when-not, no ordering relative to ads_github_contribution_status or ads_github_contribution_create_pr, and no stated prerequisites.

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