Skip to main content
Glama
Sign In

Moatless

by store.moatless
OverviewDiscussionsAdmin

Create a git credential

create_git_credential

Makes the actor a key for git to sign in to Moatless with, to clone and pull codebases they've bought. Answers with the credential to store in git's credential helper; the key is only shown now.

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": {
      "input": "<input>",
      "context": "<context>"
    },
    "name": "create_git_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as "the user" or "a buyer".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as \"the user\" or \"a buyer\".",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "input"
-]New value: +[
+  "input",
+  "context"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / input / properties / name / maxLength
      Added value: +100
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the credential is returned to be stored in git's credential helper, and critically the key is shown only once. It omits whether creating a new key invalidates prior keys and what happens at expiry, which keeps it from a 5.

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?

Two sentences with no filler, and the critical 'only shown now' warning is placed at the end where it stands out. The first sentence is clunky enough ('Makes the actor a key ... with') that it costs a little comprehension speed, but nothing is wasted.

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 credential-creation tool with no output schema, the description does the important work: it explains what is returned and that the value cannot be retrieved again. Remaining gaps are whether prior credentials are revoked and any hard expiry limit, both of which matter but are secondary to the one-time-display warning that is present.

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 50%, and the description mentions no parameters at all: neither 'days' (expiration) nor 'name' (label shown in user settings) is referenced, and the required nested 'context' wrapper is unexplained. The inner schema descriptions carry the meaning, so this sits at the baseline rather than being misleading, but the description does nothing to clarify defaults such as expiration.

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 concrete verb and resource: it creates a git credential for signing in to Moatless in order to clone and pull purchased codebases. The phrasing 'Makes the actor a key for git to sign in to Moatless with' is awkward and slightly indirect, but the outcome (a credential usable by git) is unambiguous and does not overlap with siblings such as create_coupon or create_listing.

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?

Usage is implied through the stated task ('to clone and pull codebases they've bought'), which also hints at a prerequisite: the actor must have purchased a codebase. There are no explicit when-not conditions, no mention of how this relates to listing or claiming a codebase, and no guidance on when an existing credential suffices instead of creating a new one.

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

All Moatless toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources