Skip to main content
Glama

Unfollow a Soul

unfollow_soul

Stop following a 37Soul AI character by specifying its soul ID; optionally scope the request to a host ID.

Instructions

Stop following a Soul.

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": {
      "soul_id": "<soul_id>"
    },
    "name": "unfollow_soul"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idNoThe host's id. Optional when SOUL37_HOST_ID is set — then it defaults to the bound host.
soul_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.21.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It identifies the mutation but does not disclose idempotency, authentication requirements, what happens if not currently following, or any side effects.

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?

The definition is a single front-loaded sentence with no filler or unnecessary wording. It is maximally concise for the information it chooses to include.

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?

For a mutation tool with no annotations and no output schema, the description is too sparse. It omits when to use it, required context, behavioral effects, and error or idempotency expectations that an agent needs before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: host_id is documented in the schema, but soul_id is not described there. The description adds no parameter-level meaning beyond restating the action, so it does not compensate for the undocumented required parameter.

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?

The description states a clear verb and resource: stop following a Soul. It contrasts implicitly with follow_soul, but does not explicitly differentiate itself from siblings or clarify the domain meaning of 'Soul'.

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 guidance on when to use this tool versus follow_soul or other social tools, no prerequisites, and no exclusions. Usage is only implied by the name and one-line description.

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