Skip to main content
Glama

Export tool config

export_tool_config
Read-onlyIdempotent

Exports a Studio Toolbox tool configuration by name, toolId, or id so you can copy it; returns read-only JSON or an error with available names.

Instructions

Export one Studio Toolbox tool configuration by name, toolId or id. Use this to copy a config. Use import_tool_config to save a pack for Toolbox import. Read-only. Returns JSON with the tool config, or an error and available names.

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": {
      "tool_name": "<tool_name>"
    },
    "name": "export_tool_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
tool_nameYesToolbox tool name, toolId or id to export. Non-empty string.
workspaceNoOptional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.3.0
    • addedInput schema / properties / workspace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional Studio workspace name, slug or id from list_workspaces. Omit for the active workspace.",
      +  "title": "Workspace"
      +}
  2. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / tool_name / description
      Added value: +"Toolbox tool name, toolId or id to export. Non-empty string."
  3. First observedv5.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description reinforces this with "Read-only." Beyond that it discloses the failure mode: an error plus available names when the identifier does not resolve, which is real behavioral value an agent can act on.

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?

Three short sentences, front-loaded with the verb and resource, with the sibling pointer and return/error behavior following. "Use this to copy a config" is slightly redundant with the export framing but earns its place as intent guidance.

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 rich annotations, a full output schema, and 100% schema coverage, the description only needs to cover purpose, routing and edge behavior. It does that, including the identifier-not-found case; minor gaps like the default-workspace behavior are already handled by the schema.

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 coverage is 100%, so both tool_name and workspace are fully documented in the schema. The description's "by name, toolId or id" restates the tool_name parameter description rather than adding format or disambiguation rules, and the workspace parameter is left to the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Export) and resource (one Studio Toolbox tool configuration) plus the accepted identifiers (name, toolId, id), and explicitly distinguishes itself from import_tool_config. An agent can separate this from the sibling import tool without opening either schema.

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

Usage Guidelines4/5

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

Gives a concrete use case ("Use this to copy a config") and names the alternative for the opposite direction, import_tool_config. It stops short of stating when-not to use it, but the read-vs-import split is clear.

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