Skip to main content
Glama

get_settings

Read-onlyIdempotent

Los ajustes de la persona, como los muestra la pantalla de Ajustes: · avisos: reminders (recordatorios), recaps (recaps listos), tasks (tareas que te asignan), shares (te compartieron algo), calendar (eventos, con calendar_alerts = minutos antes), colgados (lo que requiere atención, una vez por día a colgados_hora), colgados_reunion (sumarlo al aviso de una reunión), colgados_weekends, informe_vos (mail «Vos» cada informe_vos_dias). true = prendido. · cuenta: idioma, tema oscuro, pomodoro. · workspace (si se pasa workspace_id): zona horaria, cierre automático del día y digest programado (hora en la zona de la persona). Conectar el calendario, WhatsApp/Telegram, Mi voz o ClickUp/Jira se hace en la app: how_to_in_app.

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

Input Schema

NameRequiredDescriptionDefault
workspace_idNoPara ver también los ajustes de ese workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally; the description adds genuinely new behavioral detail such as calendar_alerts being minutes-before, colgados firing once per day at colgados_hora, and digest times being expressed in the person's timezone. It does not discuss permissions or whether settings can be absent, so it stops short of 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?

Purpose is front-loaded in the first line, then the bulleted field explanations are dense but each one carries information an agent cannot get from a schema-less return value. It is long, but the length is justified by the absence of an output schema.

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

Completeness5/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 must explain what is returned, and it does so across all three settings groups plus the sub-field semantics (true = on, alias meanings, timing fields). Combined with the how_to_in_app pointer, an agent has everything needed to call and interpret this tool.

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?

Schema coverage is 100% and the schema only says workspace_id shows that workspace's settings; the description goes further by naming what those workspace settings contain (timezone, auto day-close, scheduled digest, with the hour in the person's timezone). That is meaningful semantics beyond the 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?

The opening line identifies the resource precisely ('Los ajustes de la persona, como los muestra la pantalla de Ajustes') and the followed enumerations of 'avisos', 'cuenta' and 'workspace' tell an agent exactly what data comes back. It does not explicitly contrast with the sibling update_settings, though it does route integration-connection tasks to how_to_in_app.

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?

It states the conditional behavior of workspace_id ('si se pasa workspace_id') and explicitly says that connecting calendar, WhatsApp/Telegram, Mi voz or ClickUp/Jira happens in the app via how_to_in_app, which is real routing guidance. There is no explicit 'use this instead of update_settings' statement, keeping it below a 5.

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