Skip to main content
Glama

Coline

Update settings

update_settings
DestructiveIdempotent

Changes the person's Coline settings for assistants. Only the settings in set change.

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": {
      "set": "<set>"
    },
    "name": "update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
setYes

Output Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely carried by structured data. The description does add real value with partial-update semantics (keys omitted from `set` are preserved), but it never explains what the destructive hint means in practice, whether a value can be cleared, or what permissions are needed for a mutation on a person's settings.

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 short sentences with the partial-update rule front-loaded and no filler. It is efficient, though the brevity is partly the source of the gaps elsewhere rather than purely a virtue.

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?

An output schema exists, so return values need not be described. But for a destructive, non-read-only mutation whose only parameter is an untyped free-form object, the definition omits the valid setting keys, permission requirements, and the meaning of the destructive hint — the essentials an agent needs before writing to a person's settings.

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% and the single parameter is a free-form nested object with anyOf string/number/boolean values and no enumerated keys, so the description carries the burden. It does clarify that `set` is a partial merge ("Only the settings in set change"), which the schema cannot express, but it names no valid keys or value types, leaving an agent unable to know what to put in `set`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Changes the person's Coline settings for assistants" gives a verb and a resource, but the resource is vague: it never says which settings, and the sibling set (update_calendar_settings, update_messages_settings, read_settings) makes clear this is one settings surface among several that the description does not distinguish. An agent cannot tell from the text whether this is the general settings endpoint or something narrower.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no mention of alternatives such as the more specific update_calendar_settings or update_messages_settings, nor of read_settings for inspection. The only guidance-like sentence, "Only the settings in set change," describes merge behavior rather than when to select this tool.

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