Skip to main content
Glama

Feature Library

Install a part

install
Read-only

Licensed (needs a licence token that owns the part). Returns the part’s module/ files, each marked with the licence and this fetch, as resources to write unchanged into a folder of their own; plus NOTICE.md where there is one and the licence. Pin a version to be sure of what you get. Also takes a look id (e.g. splash, with a whole-library licence): the look’s stylesheet, its backdrop where it has one, the shared dials and the plain tokens, and the order to load them in.

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": {
      "id": "<id>"
    },
    "name": "install"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe part id, or a look id.
pathNoOptional: one file of it, as listed in files (e.g. module/charts.ts): returned as plain text, marked, with its SHA-256. For clients that cannot show the files as resources, or a reply too large to read at once.
versionNoOptional: the version to install (only the current one is served).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false, so the description carries the load and does so substantially: it discloses the licence-ownership auth requirement, that returned files are marked with the licence and this fetch and should be written unchanged into their own folder, that NOTICE.md is included where present, and that ordering matters for look assets. Some phrasing ('each marked with the licence and this fetch') is opaque, and error behaviour on an unowned licence is not stated.

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?

The licensing prerequisite is correctly front-loaded and the look-id case is separated into its own sentence. However, the middle sentence is a dense run-on that stacks return artifacts behind semicolons and parentheticals, which slows an agent parsing the contract.

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 must describe the return value, and it does — enumerating files, NOTICE.md, licence markings and load order. For a read-only, three-parameter tool this covers what an agent needs to call it and interpret the reply, with only error cases left unaddressed.

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 the schema already explains id, path and version, including that only the current version is served. The description reinforces id's dual role (part id or look id) and hints that path returns a single marked file with its SHA-256, but adds no syntax or format detail the schema lacks; baseline 3 applies.

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 description names a specific resource (a part's module/ files, plus a look's stylesheet, backdrop, dials and tokens) and states what comes back — files marked with the licence, NOTICE.md, and load order. It is clear what the tool yields, though the verb 'install' is slightly at odds with the fetch-and-return framing, and no sibling such as get_part is named to sharpen the boundary.

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?

It gives real prerequisites (a licence token that owns the part, or a whole-library licence for look ids) and explains when to pin a version ('to be sure of what you get') and when to pass path (clients that cannot render resources, or a reply too large to read at once). It never contrasts this with alternatives like get_part or check, so tool selection is left implicit.

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