Skip to main content
Glama

export_workspace_config

Read-onlyIdempotent

Exports the current workspace configuration as YAML, including rules, templates, and settings, so you can back it up before importing changes.

Instructions

Export the current workspace configuration as YAML, including rules, project templates, and settings. Read-only. The YAML is exactly what import_workspace_config accepts, so keep it as a backup before any import.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_workspace_config"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'Read-only' in the text is largely redundant. However the description adds genuinely new behavioral context: the output is YAML and is exactly the format import_workspace_config consumes, which matters for safe round-tripping. With annotations carrying the safety profile, this is solid added value.

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?

Three short sentences: what it exports, its safety profile, and the round-trip guarantee with import. The round-trip warning is placed where it lands before an agent acts on the file. No filler.

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 no-parameter, no-output-schema tool, the description covers format, contents, and the import compatibility contract, which is what an agent needs to use the result correctly. It does not clarify whether the YAML is returned inline or written to a file, a small remaining gap with no output schema to fall back on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; the description correctly adds nothing about arguments because there are none. The high schema coverage is moot here.

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 gives a specific verb (Export) and resource (workspace configuration) plus the exact payload contents (rules, project templates, settings) and format (YAML). The round-trip pairing with the import_workspace_config sibling makes the boundary between the two tools unambiguous.

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?

It states the intended usage context clearly: 'keep it as a backup before any import', which names the sibling tool to pair with and the moment to call it. It lacks an explicit 'when not to use' or note about alternatives beyond import, so it falls short of a 5.

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