Skip to main content
Glama

Unpin package

code_unpin
Destructive

Drop a package from the tree's import map.

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_unpin"
  }
}

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 package name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety is signaled structurally. The phrase "from the tree's import map" adds a little scope context (the entry is removed, not necessarily the underlying package), but the description never states what exactly is destroyed, whether the change is reversible by re-pinning, or that a message/audit note is recorded. Modest added value over annotations, not rich disclosure.

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?

A single front-loaded sentence with zero padding, which is structurally clean. The terseness borders on under-specification rather than verbosity, but as a conciseness measure it is efficient.

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

Completeness2/5

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

This is a destructive mutation on a 4-parameter tool with no output schema, and the description is a one-line fragment. An agent still cannot tell what a successful unpin changes in the tree, what happens if the package was not pinned, or how this interacts with code_pin. For a destructive operation, that leaves meaningful gaps.

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%, so org, tree, package, and message are already documented in the input schema, including the enum and regex patterns. The description adds no meaning beyond that — for example it never explains what the optional message is for or why org is mandatory on every call. Baseline 3 is appropriate.

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?

"Drop a package from the tree's import map" names a concrete verb (drop/remove) and a concrete resource (a package's entry in a tree's import map), which is specific enough to act on. It does not, however, distinguish itself from siblings such as code_pin, code_remove, or code_deps, so an agent must infer that this is the inverse of code_pin rather than a general package removal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no mention of when to unpin versus using code_pin's counterpart removal, no prerequisites, and no note about what state the tree must be in. The agent gets an operation but no routing logic toward or away from alternatives.

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