Skip to main content
Glama

Check out a branch and get its connection string

argon_connect
Idempotent

Retrieves a MongoDB connection string for a project branch, checking it out when needed so writes are captured as versioned history.

Instructions

Get a MongoDB connection string for a branch, checking it out if needed. Writes through that connection become versioned history.

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": {
      "project": "<project>",
      "branch": "<branch>"
    },
    "name": "argon_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorNoLabel for all native writes on this branch/run; cannot change while capture is running
branchYesBranch name
projectYesProject name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state readOnlyHint=false and idempotentHint=true, so the description's real contribution is behavioral: calling it may perform a checkout, and writes over that connection are captured as versioned history. That is genuinely useful side-effect disclosure. It stops short of saying what checkout does to concurrent sessions or whether history is committed automatically.

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 short sentences, front-loaded with the primary outcome and followed immediately by the side-effect and versioning caveat. No filler and nothing important buried.

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?

With no output schema, the description correctly implies the return value is a connection string, and it covers the key behavioral risk of versioned writes. Minor gaps remain around the checkout's effect on an already-checked-out branch and the persistence semantics of the returned connection.

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 project, branch, and actor are already documented in the schema. The description adds no meaning about the actor label or branch resolution, leaving it at the baseline for a fully described schema.

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?

Names a specific verb and resource — get a MongoDB connection string for a branch — plus the check-out side effect. It is clear enough to distinguish from siblings like argon_branch_list or argon_merge_apply, though it does not explicitly contrast with sandbox-creating siblings that may also yield connection strings.

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 only implied: an agent infers this is the tool to call when it needs a live connection for a branch. There is no explicit when/when-not guidance and no named alternative such as a sandbox tool for isolated work.

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