Skip to main content
Glama

Update text settings

update_text_settings
Idempotent

Changes your time zone and quiet hours. During quiet hours, normal texts are held until quiet hours end.

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

Input Schema

NameRequiredDescriptionDefault
quiet_endNo
time_zoneNo
quiet_startNo
quiet_hours_enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare idempotent=true, destructive=false, and openWorld=false, so the safety profile is covered. The description adds genuinely new behavioral context that annotations cannot convey: during quiet hours, normal texts are held until the window ends. It does not explain partial-update behavior or whether a user/account context is required.

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?

Two front-loaded sentences with no filler: the first names the action and targets, the second explains the consequence an agent cannot infer. Nothing is redundant.

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

Completeness3/5

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

For a small idempotent settings mutation with no output schema and robust annotations, the description is serviceable, but with four undocumented parameters it leaves format and flag semantics for the agent to guess from the raw regex.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, yet it only says 'time zone' and 'quiet hours.' It never explains the 24-hour HH:MM format for quiet_start/quiet_end, nor does it mention the quiet_hours_enabled flag or clarify that quiet hours are a start/end pair.

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?

The description states a specific verb (changes) and concrete resources (time zone, quiet hours), which clearly separates this configuration tool from the send/schedule siblings. It stops short of explicitly naming an alternative, but the resource scope is unambiguous.

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 only implied: an agent can infer 'call this to set time zone or quiet hours,' but there is no explicit when-to-use, no prerequisites, and no mention of how this relates to the send/schedule tools. No exclusions or alternatives are stated.

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