Skip to main content
Glama

Set my repository override

set_repo_override
Idempotent

Save your own .sinatrarc override fragment for this repository. Does not change another member's preferences or the repository file.

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": "set_repo_override"
  }
}

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.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds real blast-radius information beyond that: the write is confined to the caller's own preferences and does not touch other members or the repository-level file. It stops short of saying whether the fragment merges with or replaces an existing override.

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 the action front-loaded and the scope caveat immediately after. No filler, no restatement of the title, and every sentence carries information an agent needs.

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 three required params, a nested object, and no output schema, the definition covers purpose and blast radius adequately but leaves merge/overwrite semantics and the response shape unspecified. For a mutation tool accepting an arbitrary settings object, that is a meaningful remaining gap.

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% and each parameter already states its origin (repo_id from get_workspace, workspace_id from whoami, fragment as an overridable-settings object). The description adds no further meaning about fragment structure or what happens to keys not supplied, so baseline 3 applies.

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 and resource — saving a personal '.sinatrarc override fragment' for a given repository — and the word 'your own' pins the operation to the caller's personal scope. It is clear what the tool writes, though it never names the sibling clear_repo_override, so the reset path must be inferred from the name alone.

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 negative clause ('Does not change another member's preferences or the repository file') implies this is the self-scoped write path, which gives usable context. However, there is no explicit when-to-use or when-to-prefer-an-alternative statement, and no mention of clear_repo_override as the way to undo it.

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