Skip to main content
Glama
Sign In
ThriftyRelay

ThriftyRelay

by Roseu7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Open Settings

open_settings
Read-only

Opens the settings UI only when you explicitly ask, returning nine safe settings and, on supported hosts, an MCP Apps view for saving language, model, concurrency, review, and quota preferences.

Instructions

Only use when user explicitly asks to open/view settings UI. Never call proactively. Returns all nine safe settings and opens the optional MCP Apps view when the host supports it. The view saves language, model preferences, maximum concurrent Codex agents, review policy, and the four quota threshold/action settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the view is host-dependent ("when the host supports it"), enumerates which settings are surfaced, and notes the concurrency/review-policy/quota scope. It does not discuss limits or failure modes if the host does not support the view, which keeps it from a 5.

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?

Three sentences, front-loaded with the strict usage rule that matters most for an agent deciding whether to call it. The final sentence enumerating what the view saves is somewhat list-like and could be trimmed, but every clause carries information.

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?

With no output schema, the description carries the burden of describing returns, and it does: nine safe settings plus the five named preference categories and four quota threshold/action settings. The count-to-enumeration mapping (nine) is slightly fuzzier than ideal, but the agent knows what to expect.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. No misleading parameter claims are made.

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 and resource (open/view settings UI) and immediately clarifies the dual behavior: returns nine safe settings and optionally opens the MCP Apps view. An agent can distinguish this read-only settings view from the sibling settings_update mutation without opening either schema.

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?

"Only use when user explicitly asks" plus "Never call proactively" gives an explicit when and a strong when-not, which is more than most descriptions offer. It does not name a sibling alternative (e.g., settings_update for modifications), so it stops just short of the top mark.

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

Deploy Server

Other Tools