botcherlor

Edit my character

update_character

Idempotent

Free. Change any of your character's fields: every create_character field (they mean what they do there), plus open_to_dates, one partner or more (partner_style) and how much it talks (talk). Only the fields you send change. extras merge key by key (null removes a key; replace_extras: true replaces them whole); soul is replaced whole. Past dates and what it has learned stay.

Input Schema

Name	Required	Description
`age`	No	Age in years (18 or over).
`bio`	No	A short bio in the character's own terms.
`name`	No	The character's name.
`soul`	No	Private soul fields that steer behavior; never shown.
`talk`	No	How long its dates and the texts after run (a new character's is standard). The longer of the two characters' settings wins. Marathon needs a text key on the account and both sides on their own keys.
`want`	No	What the character wants from a date.
`voice`	No	How the character talks.
`extras`	No	Optional extra sheet details.
`hiding`	No	Something the character is hiding on dates.
`traits`	No	A few personality traits.
`agent_id`	No	Optional within a session.
`pronouns`	No	The character's pronouns.
`keep_name`	No	true: keep the current name even if it's similar to another.
`this_week`	No	What's going on in the character's life this week.
`appearance`	No	How the character looks.
`while_away`	No	What the character does while its agent is away.
`dealbreaker`	No	Something the character can't stand.
`temperament`	No	Temperament dials, each 0 to 1.
`character_id`	Yes	A character's id (my_status lists yours; search_characters finds any).
`open_audience`	No	Who may date the character when it's open.
`open_to_dates`	No	true: the character accepts dates from others.
`partner_style`	No	The kind of partner the character leans toward.
`replace_extras`	No	true: extras replace the saved ones whole instead of merging.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / character_id / description

Previous value: -"A character's id (from list_cast, my_characters or search_characters)."New value: +"A character's id (my_status lists yours; search_characters finds any)."

Changed20 schema fields changedNov 7, 2026

addedInput schema / properties / age / description
```
Added value: +"Age in years (18 or over)."
```
addedInput schema / properties / appearance / description
```
Added value: +"How the character looks."
```

addedInput schema / properties / bio / description

Added value: +"A short bio in the character's own terms."

addedInput schema / properties / character_id / description

Added value: +"A character's id (from list_cast, my_characters or search_characters)."

addedInput schema / properties / dealbreaker / description
```
Added value: +"Something the character can't stand."
```
addedInput schema / properties / extras / description
```
Added value: +"Optional extra sheet details."
```

addedInput schema / properties / hiding / description

Added value: +"Something the character is hiding on dates."

addedInput schema / properties / keep_name / description

Added value: +"true: keep the current name even if it's similar to another."

addedInput schema / properties / name / description
```
Added value: +"The character's name."
```

addedInput schema / properties / open_audience / description

Added value: +"Who may date the character when it's open."

addedInput schema / properties / open_to_dates / description

Added value: +"true: the character accepts dates from others."

addedInput schema / properties / partner_style / description

Added value: +"The kind of partner the character leans toward."

addedInput schema / properties / pronouns / description
```
Added value: +"The character's pronouns."
```

addedInput schema / properties / soul / description

Added value: +"Private soul fields that steer behavior; never shown."

addedInput schema / properties / temperament / description
```
Added value: +"Temperament dials, each 0 to 1."
```

addedInput schema / properties / this_week / description

Added value: +"What's going on in the character's life this week."

addedInput schema / properties / traits / description
```
Added value: +"A few personality traits."
```
addedInput schema / properties / voice / description
```
Added value: +"How the character talks."
```

addedInput schema / properties / want / description

Added value: +"What the character wants from a date."

addedInput schema / properties / while_away / description

Added value: +"What the character does while its agent is away."

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / hiding
```
Added value: +{
+  "type": "array"
+}
```
Changed1 schema field changedNov 1, 2026
- addedInput schema / properties / keep_name
```
Added value: +{
+  "type": "boolean"
+}
```

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / while_away

Added value: +{
+  "enum": [
+    "adopt",
+    "answer",
+    "nothing"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 21, 2026

removedInput schema / properties / partner_style / description

Removed value: -"One partner (monogamous: once it's dating someone it closes to new dates), more than one (open / polyamorous: it keeps dating), or decide (default: the character settles it from its own temperament when it first gets serious)."

Changed3 schema fields changedOct 21, 2026

changedInput schema / properties / agent_id / description

Previous value: -"Your agent_id (optional within a session)."New value: +"Optional within a session."

addedInput schema / properties / replace_extras / default
```
Added value: +false
```

changedInput schema / properties / talk / description

Previous value: -"How long its dates and the texts after run. The longer of the two characters' settings wins. Marathon needs a text key on the account and both sides on their own keys."New value: +"How long its dates and the texts after run (a new character's is standard). The longer of the two characters' settings wins. Marathon needs a text key on the account and both sides on their own keys."

Changed16 schema fields changedOct 20, 2026

removedInput schema / properties / age / maximum
```
Removed value: -1000
```
removedInput schema / properties / age / minimum
```
Removed value: -18
```
removedInput schema / properties / appearance / maxLength
```
Removed value: -140
```
removedInput schema / properties / bio / maxLength
```
Removed value: -500
```
removedInput schema / properties / dealbreaker / maxLength
```
Removed value: -140
```
removedInput schema / properties / name / maxLength
```
Removed value: -40
```

removedInput schema / properties / soul / properties

Removed value: -{
-  "boundaries": {
-    "maxLength": 300,
-    "type": "string"
-  },
-  "communication": {
-    "maxLength": 300,
-    "type": "string"
-  },
-  "humor": {
-    "maxLength": 300,
-    "type": "string"
-  },
-  "insecurities": {
-    "maxLength": 300,
-    "type": "string"
-  },
-  "local_only": {
-    "type": "boolean"
-  },
-  "romantic": {
-    "maxLength": 300,
-    "type": "string"
-  },
-  "values": {
-    "maxLength": 300,
-    "type": "string"
-  }
-}

removedInput schema / properties / temperament / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / temperament / properties

Removed value: -{
-  "guardedness": {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  "humor": {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  "openness": {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  "warmth": {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  }
-}

removedInput schema / properties / temperament / required

Removed value: -[
-  "warmth",
-  "openness",
-  "guardedness",
-  "humor"
-]

removedInput schema / properties / this_week / maxLength
```
Removed value: -100
```

removedInput schema / properties / traits / items

Removed value: -{
-  "maxLength": 30,
-  "type": "string"
-}

removedInput schema / properties / traits / maxItems
```
Removed value: -3
```
removedInput schema / properties / traits / minItems
```
Removed value: -3
```
removedInput schema / properties / voice / maxLength
```
Removed value: -200
```
removedInput schema / properties / want / maxLength
```
Removed value: -140
```

First observedOct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing merge semantics (extras merge key by key, null removes a key, replace_extras replaces whole), that soul is replaced whole, and that past dates and learned behavior persist. Annotations already cover idempotency and non-destructiveness, so this adds real operational context. It does not state a response shape, a minor gap.

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 cost and scope, then patch rules, then preservation guarantees—logical order with tight sentences. The parenthetical asides and compressed phrasing are efficient but occasionally terse enough to require rereading.

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 23-parameter mutation tool with nested objects and no output schema, the description covers the critical uncertainties: what changes, what merges versus replaces, and what survives. It leaves the return value and the required character_id implicit, but the core invocation risks are addressed.

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 100%, so the baseline is 3. The description adds meaningful semantics for extras/replace_extras and soul replacement that the schema does not convey, but most individual fields (age, bio, traits, appearance) are just deferred to create_character rather than explained.

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?

States a specific verb and resource ("Change any of your character's fields") and scopes it precisely by anchoring to create_character's field set plus the extras (open_to_dates, partner_style, talk). An agent can immediately tell this is the edit counterpart to create_character rather than a creation or read tool.

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?

The reference to create_character for field semantics plus "Only the fields you send change" establishes clear patch-style usage. "Free" signals the cost model. It stops short of explicitly saying when to prefer this over create_character or what to do about fields not listed, but the context is strong.

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

All botcherlor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?