Skip to main content
Glama
Qumge

37soul-mcp

by Qumge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

List your 37Soul hosts

list_hosts

Retrieve a paginated directory of your 37Soul AI characters with id, nickname, age, and karma. Use limit and offset to page, and get_host for character or greeting details.

Instructions

List the AI characters (hosts) you created on 37Soul as a compact directory (id, nickname, age, karma). Default page size is 20. Use get_host for character/greeting details. Pass limit/offset to page.

Input Schema

NameRequiredDescriptionDefault
limitNoMax hosts per page (default 20, max 50). Use with offset to page.
offsetNoNumber of hosts to skip (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.11.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max hosts per page (default 20, max 50). Use with offset to page.",
+  "maximum": 50,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of hosts to skip (default 0).",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the default page size (20), the paging parameters, and the compact shape of the returned directory (id, nickname, age, karma) — useful context. It does not state that this is a safe read-only operation, what permissions are needed, or what happens past the max limit/page boundary.

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?

Three short sentences, front-loaded with what is listed and what is returned, followed by the routing hint and the paging instruction. No filler text.

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?

There is no output schema, and the description compensates by enumerating the returned fields (id, nickname, age, karma), which an agent would otherwise have to discover. Scope, paging, and the alternative tool are all covered; only safety/permission context is absent for a simple read tool.

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 limit and offset are already fully documented in the schema, including the default 20 and max 50. The description repeats the default page size and paging intent without adding syntax or behavior beyond the schema; baseline 3 is appropriate.

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 (List) and resource (AI characters/hosts you created on 37Soul), and immediately names the sibling it is not by pointing to get_host for detail. An agent can distinguish it from get_host and update_host without opening either 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?

Explicitly routes the agent: use get_host for character/greeting details, and states the paging mechanism (limit/offset). However it gives no negative guidance such as when not to use this tool or what set of hosts is excluded, so it stops short of full when/when-not coverage.

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