Skip to main content
Glama
Sign In
ThriftyRelay

ThriftyRelay

by Roseu7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Save Settings

settings_update

Submit updated user-facing settings to configure model selection, review policy, language, agent count, and 5-hour or weekly quota thresholds with warn or block actions.

Instructions

Internal settings form submission. Accepts only the nine user-facing settings fields, including independent 5h and 1w quota thresholds and warn/block actions.

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

Input Schema

NameRequiredDescriptionDefault
languageNo
baseModelNo
upperModelNo
reviewPolicyNo
maxCodexAgentsNo
weeklyLimitActionNo
weeklyLimitPercentNo
fiveHourLimitActionNo
fiveHourLimitPercentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds the important constraint that only the nine user-facing fields are accepted, but it never says whether omitted fields are preserved or reset to defaults — a critical ambiguity for a mutation with zero required parameters.

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 tight sentences with no filler, and the scope constraint (only nine user-facing fields) is front-loaded where it matters most. Slightly dense phrasing ('independent 5h and 1w quota thresholds') but nothing wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with nine parameters at 0% schema coverage, zero required fields, and no output schema, the description should explain update semantics (merge vs replace), auth requirements, and what the remaining model/policy fields control. It covers only the quota fields, leaving an agent guessing about half the surface.

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 0%, so the description could compensate but only partly does: it calls out the independent 5h and 1w quota thresholds and the warn/block actions, which clarifies four of the nine fields. language, baseModel, upperModel, reviewPolicy, and maxCodexAgents remain undocumented in both description and schema.

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?

Identifies the tool as the write side of the settings form ('Internal settings form submission'), which distinguishes it from the sibling open_settings reader. The verb is implied rather than stated outright ('submission', 'accepts'), so it is clear but not razor-sharp.

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?

No explicit when/when-not statement and no mention of open_settings as the read counterpart, but 'Internal settings form submission' implies this is the write path an agent should use after reading settings. There are no exclusions or prerequisites (auth, admin scope) stated.

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