Skip to main content
Glama

tree_package

The semantic package library — capitalized vocabulary, rules and solvers, shared across every account on this server. No arguments: list the library and this workspace's pins.

Instructions

The semantic package library — capitalized vocabulary, rules and solvers, shared across every account on this server. No arguments: list the library and this workspace's pins. install='name@version' pins a package — its whole dependency closure applies (its requires, transitively), your own entries always winning; a broken closure (missing dep, two versions of one name) is refused at pin time, and so is a name (kind, rule or solver) two pinned packages both define when neither requires the other. prefer={name: package} says which package's definition this workspace uses for such a name, alone or with install; an entry that settles no clash is refused. The pin records the package's content digest, so it keeps meaning these exact semantics even against another library. uninstall removes the pin. publish submits {name, version, description, requires: [{name, version}], vocabulary, rules, solvers: [{name, description, reads, wasm_b64, medium: wasm|web|prose}], examples}. Publishing is proof-gated: every rule must be exercised by the package's own examples and pass — examples run with the requires closure staged beneath, so extending packages prove themselves in the semantics they will live in; every wasm solver must meet the ABI (web/prose artifacts are stored content-addressed, served from artifact://{sha}, never executed). requires pin exact versions of already-published packages. Versions are immutable — ship a new one to evolve.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
preferNo
installNo
publishNo
uninstallNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.9
    • addedInput schema / properties / prefer
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Prefer"
      +}
  2. First observedv0.1.2

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses refusal conditions (broken closures, duplicate names, no-op prefer entries), that pins record a content digest for semantic stability, that versions are immutable, that publishing is proof-gated by the package's own examples, and that web/prose artifacts are content-addressed and never executed. Auth requirements and error surface beyond 'refused' are not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Information density is high and the resource identity is front-loaded, but the entire definition is one long run-on paragraph mixing five distinct modes, making it easy to lose mode boundaries. Bulleted or per-mode segmentation would substantially improve scannability without adding length.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers all five modes plus the dependency-precedence algorithm and the publish payload shape. The only ambiguity left is what the lone `name` argument does outside prefer.

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 0%, so the description must compensate, and it largely does: it specifies install's 'name@version' format, prefer's {name: package} mapping and its interaction with install, uninstall's effect, and a full field list for publish including requires/vocabulary/rules/solvers/examples with medium values. The bare `name` parameter is the one gap — its standalone role is never stated.

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 opening sentence names the resource precisely ("the semantic package library — capitalized vocabulary, rules and solvers, shared across every account") and the description then enumerates each operation mode: listing (no args), install, prefer, uninstall, publish. It's clear what the tool operates on, though it never explicitly distinguishes itself from siblings like tree_vocabulary, tree_rule or tree_solver.

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 mode semantics imply when each argument applies ("No arguments: list the library", "install='name@version' pins a package", "uninstall removes the pin"), and it explains when prefer is needed. However, there is no guidance on when to call this versus the sibling package/rule/vocabulary tools, and no explicit 'when not to use' exclusions.

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