Skip to main content
Glama

Check a draft repository override

preflight_repo_config
Read-onlyIdempotent

Check a draft .sinatrarc fragment against your effective config and available model credentials without saving it. Any workspace member.

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": {
      "workspace_id": "<workspace_id>",
      "repo_id": "<repo_id>",
      "fragment": "<fragment>"
    },
    "name": "preflight_repo_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_idYesThe repository id from get_workspace.
fragmentYesA .sinatrarc override fragment; only the dashboard's overridable settings are accepted.
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only and idempotent, and the description adds real value beyond them: nothing is persisted, and the check runs against both the effective config and available model credentials — a non-obvious cross-check. It does not disclose what the result looks like (errors vs. warnings, whether it aborts), and there is no output schema to cover that.

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?

One front-loaded sentence carrying purpose, the no-save constraint, and the credential check; the trailing 'Any workspace member.' earns its place by stating permissions, though as a verbless fragment it reads slightly clipped.

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?

With no output schema, the description should explain what a check returns (pass/fail, per-setting diagnostics, credential warnings) and it does not, nor does it address how nested fragment keys are validated. Adequate to select the tool, thin on what to expect back.

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 parameters are already documented, and the description only restates that the fragment is a draft .sinatrarc override evaluated against the effective config. It adds no syntax, size, or shape guidance for the nested fragment object beyond what the schema says.

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 (check) and resource (draft .sinatrarc fragment) with the key scope qualifier 'without saving it', which implicitly separates it from set_repo_override. It does not name a sibling explicitly, but the read-only dry-run nature is 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?

The 'draft ... without saving' framing makes the when-to-use case clear: validate before persisting. It also states the permission bar ('Any workspace member'), but never explicitly says to call this before set_repo_override or what to do if the check fails, so the routing is implied rather than spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources