Skip to main content
Glama

contentrain_submit

Idempotent

Push cr/* branches to the remote so the platform can handle PR creation. Use this instead of pushing branches or opening pull requests manually.

Instructions

Push cr/* branches to remote. MCP is push-only — PR creation is handled by the platform. Do NOT manually push or create PRs.

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": "contentrain_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional message for the push operation
branchesNoSpecific branch names to push (omit for all cr/* branches)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.61
    • changedInput schema / properties / branches / description
      Previous value: -"Specific branch names to push (omit for all contentrain/* branches)"New value: +"Specific branch names to push (omit for all cr/* branches)"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already disclose non-readonly, non-destructive, idempotent behavior. The description adds useful operational context beyond annotations: the tool is push-only and PR creation is handled externally, with an explicit warning not to manually push or create PRs. It does not describe authentication, failure modes, or return behavior, but is meaningfully more informative than the annotations alone.

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?

The description is two short sentences, front-loads the action and scope, and every phrase carries operational meaning. There is no redundant restatement of the tool name or schema.

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?

For a low-complexity two-parameter push tool with complete schema descriptions and annotations, the description provides enough context to invoke it correctly. It does not explain success/failure or return behavior, and no output schema exists, leaving a minor completeness gap.

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 description coverage is 100%, and the schema already explains the optional message and branches parameters, including that omitting branches targets all cr/* branches. The description adds little parameter-level detail beyond the schema baseline.

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 states a specific verb and resource: push cr/* branches to remote. It also clarifies the boundary that MCP is push-only and PR creation is handled by the platform, which helps distinguish this tool from PR-creation workflows.

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?

It gives clear usage context: use for pushing cr/* branches, and do not manually push or create PRs because the platform handles PR creation. It does not explicitly route the agent away from sibling tools such as contentrain_merge or contentrain_apply, so it stops short of full alternatives guidance.

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