Skip to main content
Glama
Sign In
mcp-fabric-api

mcp-fabric-api

by mkoziel2000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

environment_export_published_external_libraries

Read-only

Export published external libraries into an environment.yml file and write it to a specified path, making dependencies portable for environment replication and management.

Instructions

Export the published external libraries as an environment.yml file. Writes the yaml to disk.

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": {
      "workspaceId": "<workspaceId>",
      "environmentId": "<environmentId>",
      "outputFilePath": "<outputFilePath>"
    },
    "name": "environment_export_published_external_libraries"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdYesThe workspace ID
environmentIdYesThe environment ID
outputFilePathYesFile path where the environment.yml content will be written

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds a meaningful behavioral detail: it writes the yaml to disk, which is a side effect not captured by annotations. It does not, however, describe overwrite behavior or error conditions.

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

Conciseness5/5

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

Two short sentences with no filler. The core action and side effect are front-loaded, and every word earns its place.

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?

For a simple three-parameter tool with full schema coverage and annotations already covering safety, this description is largely complete. The only minor gap is not explicitly stating that the environment must already have published external libraries, but the 'published' qualifier makes that reasonably clear.

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 documents all three parameters. The description only reinforces that outputFilePath receives the environment.yml content, adding no new semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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?

The description uses a specific verb ('Export'), names the resource ('published external libraries'), and states the concrete output ('environment.yml file'). It clearly differentiates from the sibling tool environment_export_staging_external_libraries by specifying 'published' rather than 'staging'.

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 description implies this tool is for published external libraries, and the sibling name environment_export_staging_external_libraries provides an alternative. However, it does not explicitly state when to use this tool versus the staging export, nor does it mention prerequisites such as the environment needing to be published first.

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

Deploy Server

Other Tools