Skip to main content
Glama

Set the workspace model default

set_model_default
Idempotent

Save a catalog engine/model pairing and optional effort as the workspace default for future tasks. Does not change running tasks. Workspace owners only; repeating the same selection has the same effect.

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>",
      "engine": "<engine>",
      "model": "<model>"
    },
    "name": "set_model_default"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesAn exact model id in the engine's Sinatra catalog, e.g. opus-5-5 for claude-code or anthropic/claude-opus-5-5 for oh-my-pi.
effortNoOptional reasoning effort for the selected model.
engineYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false. The description adds genuinely new behavioral facts: the change does not affect running tasks, and the caller must be a workspace owner. The sentence "repeating the same selection has the same effect" largely restates idempotentHint rather than adding information.

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 with zero waste, front-loading the action and following with the two constraints an agent most needs (no effect on running tasks, owner-only). Nothing is buried or redundant enough to remove except the idempotency restatement.

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 small, non-destructive, idempotent mutation with no output schema, the description covers the action, its temporal scope, and its permission gate. It stops short of saying whether the change takes effect immediately or what confirmation is returned, which is a minor 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 75%, so the schema already documents model, effort, and workspace_id. The description only restates that engine/model are a catalog pairing and effort is optional, adding no new semantics; the engine enum in particular remains undocumented in both places, but the gap is small.

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?

States a specific verb ("Save") plus the exact resource ("a catalog engine/model pairing and optional effort") and its scope ("as the workspace default for future tasks"). The clause "Does not change running tasks" further pins down what kind of change this is, distinguishing it from anything that mutates live tasks.

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?

Usage is implied rather than stated: "for future tasks" and "Workspace owners only" tell you the context and prerequisite, but no alternative tool (e.g. clearing or reading the default) is named and no explicit when-not guidance is given. An agent can infer this is the write counterpart to get/clear default only from sibling names, not from the description.

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