Skip to main content
Glama

Set a personality dial (gated, style only)

set_trait

Adjust Iris's style dials (humor, verbosity, bluntness, proactivity, warmth) on a 0–100 scale. Changes require owner approval, apply on the next turn, and can be durable or session-only.

Instructions

Adjust one of Iris's STYLE dials on a 0–100 scale: humor, verbosity, bluntness, proactivity, warmth. This is a GATED action — it pauses for the owner's one-time approval, then takes effect on the NEXT turn (no /new needed). Use scope: "durable" (default) to change the standing default, or scope: "session" for a temporary runtime override that leaves the durable default intact. Higher = more of that trait. You CANNOT dial truth, accuracy, verify-before-claim, safety, or Rule-of-Two — those are invariants, not dials, and the tool will refuse them. Call this only when the owner asks to change your style.

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": {
      "trait": "<trait>",
      "level": "<level>"
    },
    "name": "set_trait"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYes0–100 (integer). Higher = more of the trait.
scopeNo"durable" (default) = standing change; "session" = temporary override, durable default kept.
traitYesStyle trait: humor | verbosity | bluntness | proactivity | warmth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the gated one-time owner approval, that the change lands on the NEXT turn without /new, and that invariant traits are rejected by the tool. It does not say what the refusal or success response looks like, which is the remaining gap for a mutation tool.

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?

Front-loaded with the core action and the scale, then the gating behavior, then the scope choice, then the exclusion. Every sentence is doing work, though the density of em-dash clauses makes it slightly heavier than it needs to be.

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?

For a three-parameter mutation with no annotations and no output schema, the description covers activation conditions, latency, refusal semantics, and scope differences. Only the response/return behavior and any limits on repeated changes are left unstated.

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% (baseline 3), and the description still adds orientation the schema lacks: 'Higher = more of that trait' frames the numeric direction, and it clarifies that session is a runtime override that leaves the durable default intact. Those points are echoed in schema text, so the added value is real but modest.

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?

The description names a specific verb and resource ('Adjust one of Iris's STYLE dials on a 0–100 scale') and enumerates the exact dial set (humor, verbosity, bluntness, proactivity, warmth). It also draws a hard boundary against non-style traits, so an agent can tell this apart from any brain-edit or personality-reset sibling.

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

Usage Guidelines5/5

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

It states the trigger explicitly ('Call this only when the owner asks to change your style') and adds an exclusion list (truth, accuracy, verify-before-claim, safety, Rule-of-Two are invariants and will be refused). The scope choice is also given a decision rule: durable for standing defaults, session for temporary overrides.

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