Skip to main content
Glama

Update a 37Soul host profile

update_host

Modify low-risk host profile fields—character, greeting, or preferred channels—without altering billing, visibility, or publishing automation.

Instructions

Update low-risk owner profile fields for a host: character, greeting, or preferred channels. This cannot change billing, visibility, or publishing automation.

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": {
      "host_id": "<host_id>"
    },
    "name": "update_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe host's positive integer id (from list_hosts).
greetingNoUpdated greeting text (up to 800 characters; use an empty string to clear it).
characterNoUpdated character/personality text (up to 1,000 characters).
preferred_channel_idsNoPreferred channel ids, replacing the existing list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / host_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / preferred_channel_ids / items / maximum
      Added value: +9007199254740991
  2. Addedv0.11.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It usefully classifies the operation as low-risk and states what cannot be changed, but it omits permission requirements, reversibility, and partial-update semantics.

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 tight sentences, front-loaded with the action and field scope, followed by a critical exclusion. No filler wording.

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 mutation tool with no annotations and no output schema, the description covers purpose, editable fields, and key exclusions. It leaves out auth requirements, whether omitted fields are preserved, and what a successful response contains, so it is adequate but not fully complete.

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 coverage is 100% and each parameter is well documented, including host_id provenance and empty-string clearing for greeting. The description only restates the field names and adds no syntax or update-semantics detail 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?

States a specific verb (Update) and resource (host profile fields) and enumerates the exact editable fields: character, greeting, and preferred channels. The mutation intent is unambiguous, though it does not explicitly distinguish itself from read-oriented siblings like get_host.

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?

Gives clear context by naming the only fields it can change and explicitly excluding billing, visibility, and publishing automation, which tells the agent when not to use it. It stops short of naming alternative tools for those excluded changes or stating prerequisites such as owner permissions.

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