Skip to main content
Glama

pull_place

DestructiveIdempotent

Refreshes a connected place's disk mirror by re-reading all Studio scripts and rewriting the folder to match; use when files look stale. Git-enabled places commit any uncommitted mirror changes first.

Instructions

Re-read every script in a connected place and rewrite its mirror folder on disk (/projects/_) to match Studio. It runs automatically on connect, so use it only when the files look out of date. Mirror files are overwritten; when git is on, uncommitted mirror changes are committed first so they can be recovered. Unpublished places (PlaceId 0) have no mirror.

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

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds substantive behavior beyond them: mirror files are overwritten, uncommitted mirror changes are committed first when git is on so they can be recovered, and unpublished places have no mirror at all. That is exactly the side-effect and recovery context an agent needs before a destructive rewrite.

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?

Four tight sentences, front-loaded with the action, then the auto-run caveat, then the overwrite/git-recovery behavior, then the PlaceId 0 exception. No filler and nothing that could be cut without losing information.

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

Completeness5/5

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

This is a destructive, auto-triggered rewrite with no output schema, and the description covers side effects, recovery path, trigger timing, and the unmirrored-place edge case. An agent has everything needed to decide whether to call it and what will happen.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the single parameter's effect: the mirror path is derived from place name and placeId, and PlaceId 0 means no mirror exists. It does not restate the default-to-bound-place behavior, so it is not a full 5.

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?

States a specific verb and resource: re-read every script in a connected place and rewrite its mirror folder on disk. It even names the exact target path pattern (<project>/projects/<name>_<placeId>) and the no-op case (PlaceId 0), so an agent knows exactly what this does without opening the schema.

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?

Gives an explicit when-to-use condition ("use it only when the files look out of date") and a when-not signal (it already runs automatically on connect). It does not name a sibling alternative such as git_pull, so it falls short of a 5, but the guidance is clear enough to act on.

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