Skip to main content
Glama

Pin package

code_pin
Destructive

Add an npm package to the tree's import map at an exact version (the latest unless a version, range or tag is given), so files import it by name. Its subpaths resolve too.

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": {
      "tree": "<tree>",
      "package": "<package>",
      "org": "<org>"
    },
    "name": "code_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgYesslug of the organization whose trees and sites to use. Required on every call, even when only one organization is listed; a path never names it.
treeYesThe tree's name.
messageNoA brief note on the change.
packageYesThe npm package name, e.g. preact or @preact/signals.
versionNoA version, range or tag.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and readOnlyHint=false, so the agent knows this mutates and reaches outside. The description adds real value with the default-version rule and subpath resolution, but never warns that an existing pin may be overwritten or that the import map is mutated — the concrete meaning of destructiveHint here is left implicit.

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?

One sentence, front-loaded with the action and resource, followed by the practical payoff (import by name) and the subpath note. Nothing is redundant or padded.

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?

Five parameters with three required and no output schema; the description covers the core write and its default but says nothing about the required org/tree scoping, the optional change message, or what a successful pin returns. Adequate for a simple mutation, but not fully complete against the schema's required fields.

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 the baseline is 3; every parameter including org, tree, message, package, and version is already documented in the schema. The description only adds the default semantics that version falls back to 'latest', which is a useful but small increment over structured data.

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?

States a specific verb and resource ('Add an npm package to the tree's import map') and explains the resulting behavior ('files import it by name'). It never names the opposing sibling code_unpin, so the agent must infer that removal lives elsewhere, which keeps it from a 5.

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?

The purpose implies when to call it (you need a package importable by name), but there is no explicit 'use this when / not when' framing and no reference to alternatives such as code_unpin for removal or code_update for changing a pin. Usage is inferable but not stated.

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