Skip to main content
Glama

Get the workspace model default

get_model_default
Read-onlyIdempotent

Read the workspace's saved engine, model and optional effort, or null when automatic selection applies. Any workspace member. Reads only.

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>"
    },
    "name": "get_model_default"
  }
}

Input Schema

NameRequiredDescriptionDefault
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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds genuine value beyond them by disclosing the return semantics — the saved engine/model/effort, or null when automatic selection applies — which the annotations say nothing about. It stops short of describing output shape or failure behavior.

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?

Two short sentences, front-loaded with the read action and its return contract. "Reads only" mildly restates the readOnlyHint annotation and "Any workspace member" is terse to the point of ambiguity, but no sentence is wasted.

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 single-parameter read tool with full annotations and no output schema, the description covers the essential gap — what comes back, including the null case. Only minor omissions remain, such as error behavior for an unknown workspace id or how the returned default interacts with model keys.

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?

There is a single parameter with 100% schema description coverage, including a pointer to whoami as the source. The description adds no further meaning about workspace_id (e.g. what happens on an invalid or inaccessible id), so the schema does all the work and the 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?

Specific verb (read) plus the exact resource (workspace's saved engine/model/effort) and even the null-when-automatic outcome. An agent can distinguish it from set_model_default and clear_model_default by inference, but neither sibling is named, so the differentiation is implicit rather than explicit.

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 description supplies caller eligibility ("Any workspace member") and mode ("Reads only"), which tells the agent it can be called without elevated permissions. It never states when to prefer this over checking defaults another way, nor references set_model_default or clear_model_default as the mutation counterparts, so guidance 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