Skip to main content
Glama

import_protocols

Load protocol definitions from a bundle file or inline bundle, with conflict resolution strategies and dry-run validation.

Instructions

Import protocols from a bundle file or inline bundle. Supports conflict resolution strategies and dry-run mode.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "import_protocols"
  }
}

Input Schema

NameRequiredDescriptionDefault
bundleNoInline bundle object to import
dryRunNoValidate but don't actually import (default: false)
bundlePathNoPath to bundle file to import
projectDirYesAbsolute path to the project directory
verifySignatureNoVerify bundle signature if present (default: true)
activateImportedNoActivate imported protocols immediately (default: false)
conflictStrategyNoHow to handle conflicts (default: skip)
validateDependenciesNoValidate dependencies exist (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries full burden. It does disclose two meaningful behaviors beyond the schema's bare defaults: conflict resolution strategies exist and dry-run is available, which signals this is a mutating operation that can overwrite or rename existing protocols. It stops short of saying what gets destroyed under each strategy, whether imports are reversible, or what permissions are needed.

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?

Two tight sentences with zero filler, and the core action is front-loaded before the capability clause. Slightly more could have been spent on the mutating consequences rather than the feature list.

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?

For an eight-parameter mutation tool with a nested bundle object, no output schema, and no annotations, the description is thin on behavioral consequences. It never addresses the required projectDir scope, signature verification implications, or what the import returns, relying entirely on the schema for those.

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 all eight parameters including the nested bundle object are already documented, making 3 the baseline. The description adds only that conflict strategies and dry-run exist, without explaining semantics of individual strategies like merge or newest beyond the enum labels.

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+resource ("Import protocols from a bundle file or inline bundle") and names the two accepted sources, which clearly separates it from export-style operations. It does not explicitly distinguish itself from nearby siblings such as sync_protocols or validate_feature_protocols, so an agent must infer 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?

The two source modes (bundle file vs inline bundle) give a mild selection cue, and the mention of dry-run implies a validate-first workflow. However, there is no explicit when-to-use guidance, no prerequisites, and no statement of when to prefer sync_protocols or validate_feature_protocols instead.

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