Skip to main content
Glama

Open workspace model key settings

model_key_settings
Read-onlyIdempotent

Return the dashboard URL where a workspace admin or owner can securely add a shared API key. Does not open the page or change settings. Never paste secrets into MCP. 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": "model_key_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is largely covered. The description still adds genuine context: it returns a URL rather than performing an action, it never opens the page, and secrets must never be pasted into MCP. It does not say what the response looks like beyond being a URL or what happens for non-admin members despite the 'Any workspace member' note.

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?

Five short front-loaded sentences, with the core return value stated first. 'Does not open the page or change settings' and 'Reads only' partially overlap, a minor redundancy, but nothing is padded.

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 simple single-parameter read tool with no output schema, the definition covers what is returned, what is not done, and the permission scope. Minor gaps remain around URL lifetime or behavior for non-admin callers, but nothing essential to invoking it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter, and the schema fully documents workspace_id with its provenance ('from whoami'). The description adds no further parameter meaning, but at 100% coverage and a single required param the schema carries that load adequately.

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 return value: it returns the dashboard URL where a shared API key can be added, and explicitly negates opening the page or changing settings. This makes the read-only nature unmistakable, though it does not name a sibling such as list_model_keys to route the agent between them.

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?

Implies the when: a workspace admin or owner needing to add a shared API key should call this to obtain the URL. 'Does not open the page or change settings' and 'Never paste secrets into MCP' rule out the wrong usage pattern, but no alternative tool is named when the caller actually wants to manage or list keys.

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