Skip to main content
Glama

export_protocols

Creates a portable, shareable bundle of protocols that other MCP instances or team members can import, with optional tag filtering, dependency inclusion, and integrity signing.

Instructions

Export protocols to a shareable bundle. Creates a portable bundle that can be imported by other MCP instances or shared with team members.

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

Input Schema

NameRequiredDescriptionDefault
nameNoBundle name (auto-generated if not provided)
filterTagsNoOnly include protocols with these tags
outputPathNoFile path to save the bundle (optional)
projectDirYesAbsolute path to the project directory
signBundleNoSign the bundle for integrity verification (default: true)
descriptionNoBundle description
protocolIdsNoSpecific protocol IDs to export (empty = all active)
includeInactiveNoInclude inactive protocols (default: false)
includeDependenciesNoInclude all dependencies of selected protocols (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden. It says a bundle file is created but never states whether an existing file at outputPath is overwritten, whether the project directory is modified, what permissions are required, or where the bundle ends up if outputPath is omitted — significant gaps for a tool that writes to disk.

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 short sentences with the core action front-loaded. The second sentence partly restates the first ('portable bundle' repeats 'shareable bundle'), but there is no meaningful bloat.

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 nine-parameter write tool with no annotations and no output schema, yet the description says nothing about the returned value (e.g., resolved bundle path or name) or the overwrite/error behavior that an agent needs before calling it. Relative to its complexity, it leaves too much undisclosed.

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 every one of the nine parameters is already documented, including defaults for signBundle, includeInactive, and includeDependencies. The description adds no semantics beyond the schema, so the baseline of 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?

States a specific verb+resource ('Export protocols to a shareable bundle') and clarifies the artifact is portable and importable by other MCP instances. It is clearly distinguishable from import_protocols by direction of data flow, but it never names a sibling explicitly.

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 phrase 'can be imported by other MCP instances or shared with team members' implies when this is useful, but there is no explicit when-to-use guidance or exclusion relative to sync_protocols or import_protocols. The agent must infer the choice from the name alone.

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