Skip to main content
Glama

setup_configure

DestructiveIdempotent

Saves shared setup progress for cluster, background, and notifications—storing SSH aliases, never passwords—so simulation workflows retain consistent configuration.

Instructions

Save shared setup progress. Sections: cluster, background, notifications. Store SSH aliases, never passwords. For one project's background preference use task_background instead of changing this shared setting.

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": {
      "section": "<section>",
      "values": "<values>",
      "op_id": "<op_id>"
    },
    "name": "setup_configure"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
valuesYes
sectionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the operation is idempotent, destructive, and not read-only; the description adds genuinely new context that SSH aliases may be stored but passwords must never be, which is important safety guidance. However, it does not explain what destructive behavior means in practice, such as whether saving a section replaces the existing shared settings for that section, leaving the most consequential trait undescribed.

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, front-loaded with the action and scope, followed by the section list, the secret-handling rule, and the sibling alternative. Every sentence adds distinct information with no redundancy.

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?

An output schema exists and annotations cover idempotency and destructiveness, so the description only needs to cover the gaps. It still leaves the nested values structure and op_id purpose unexplained for a three-parameter required write operation, which is the main incompleteness.

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 0%, so the description should carry the burden, and it partially does, giving the allowed section values (cluster, background, notifications). It says nothing about the shape or contents of the nested values object or what op_id is for, so two of the three parameters remain undocumented anywhere.

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?

The description gives a specific verb and resource ("Save shared setup progress") and enumerates the three sections (cluster, background, notifications), which concretely scopes the tool. It also names a sibling (task_background) as the route for a narrower use case, so an agent can separate the two without reading schemas, though "setup progress" remains somewhat abstract.

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 an explicit exclusion: for a single project's background preference, use task_background instead of changing this shared setting. Implicitly, this tool is the shared/global configuration path, but the description never states when the tool should be used versus those sibling tools for cluster or notification settings, so guidance is clear but not exhaustive.

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