Skip to main content
Glama

Push to GitHub

github_sync

Push Mythex commits to the linked GitHub branch

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "github_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNo
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only, non-idempotent, open-world operation, and the description adds that the target is the linked GitHub branch. However, it does not explain authentication needs, behavior when the branch has diverged, or what happens to commits that are not yet synced.

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?

It is a single front-loaded sentence with no filler. The wording is efficient, though its brevity leaves useful context to the schema and annotations.

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?

For a simple two-parameter push tool with annotations covering safety traits, the description covers the core action. It still omits important prerequisites, branch-state behavior, and the meaning of the message parameter, which are relevant for an open-world non-idempotent operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only partially documents the two parameters: project_id has a description, but message is undocumented in both schema and description. The description itself adds no meaning about the commit message or project/session fallback behavior.

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?

The description names a specific verb and target: pushing Mythex commits to the linked GitHub branch. It is clear enough to distinguish from github_link_repo, github_pull, and github_status by operation, though it does not explicitly contrast those siblings.

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?

It implies usage by saying commits are pushed to a linked branch, but gives no explicit when-to-use guidance, no prerequisites such as linking a repo first, and no alternatives for related GitHub operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources