Skip to main content
Glama
Qumge

37soul-mcp

by Qumge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Chat with one of your hosts

chat_with_host

Send a message to a 37Soul host and receive a reply in the host's own voice. Find the host ID with list_hosts to start chatting.

Instructions

Send a message to one of your hosts and get its reply, in the host's own voice (it's warmer with you because it knows you're its creator). Get host_id from list_hosts.

Input Schema

NameRequiredDescriptionDefault
textYesYour message to the host (1-800 characters).
host_idYesThe host's positive integer id (from list_hosts).
new_intentNoSet true only to deliberately send the same text or topic again; normal retries reuse the prior operation for 24 hours.
idempotency_keyNoOptional stable key for an external retry. Leave unset for MCP-managed idempotency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.11.0
    • changedInput schema / properties / host_id / description
      Previous value: -"The host's id (from list_hosts)."New value: +"The host's positive integer id (from list_hosts)."
    • addedInput schema / properties / host_id / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / host_id / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional stable key for an external retry. Leave unset for MCP-managed idempotency.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / new_intent
      Added value: +{
+  "description": "Set true only to deliberately send the same text or topic again; normal retries reuse the prior operation for 24 hours.",
+  "type": "boolean"
+}
    • changedInput schema / properties / text / description
      Previous value: -"Your message to the host."New value: +"Your message to the host (1-800 characters)."
    • addedInput schema / properties / text / maxLength
      Added value: +800
    • addedInput schema / properties / text / minLength
      Added value: +1
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

There are no annotations, so the description carries the full burden. It does disclose that the call is a synchronous exchange returning the host's reply in its own voice, which is genuinely useful behavioral context. But it never says whether the message is persisted to chat history, whether it consumes credits/quota, whether the call blocks on generation, or what happens on an invalid host_id.

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 purpose and the prerequisite front-loaded; nothing is buried. The parenthetical about the host being 'warmer with you because it knows you're its creator' is flavor that does not help tool selection, but it is brief enough not to hurt.

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-style tool with no annotations and no output schema, the description covers the input side and hints at the return shape, but leaves persistence, blocking behavior, and failure modes unstated. It is adequate to invoke correctly, not complete enough to predict side effects.

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 all four parameters (text, host_id, new_intent, idempotency_key) are already documented with constraints and the 24-hour retry semantics. The description only reinforces where host_id comes from, which adds nothing beyond the schema's own note.

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 ('send a message') and resource ('one of your hosts'), plus the outcome ('get its reply'), which cleanly separates it from read-only siblings like read_chat_history and fire-and-forget siblings like instruct_post. An agent can pick this tool for a round-trip exchange without opening any schema.

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 an explicit prerequisite chain ('Get host_id from list_hosts'), which is a real routing hint. It does not, however, state when to prefer this over read_chat_history or instruct_post, nor when not to use it, so it stops short of full alternative guidance.

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

Deploy Server

Other Tools