Skip to main content
Glama

Read one of your 37Soul hosts

get_host

Fetch the editable profile for one host you own, including character details, greeting, and preferred channel IDs.

Instructions

Read the full editable profile of one host you own, including character, greeting, and preferred channel ids.

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": "get_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesThe host's positive integer id (from list_hosts).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does establish that this is a read operation, that it returns an editable profile, and that ownership is required, but it says nothing about failure modes (id not found, host not owned), permissions, or whether reads have 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?

One sentence, front-loaded with the verb and resource, no filler. The returned fields are named in-line rather than left to a separate sentence.

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 one-parameter read tool with no output schema, naming the returned fields (character, greeting, preferred channel ids) covers the main gap a missing output schema would create. The remaining gap is error/permission behavior when the id is invalid or not owned.

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% and the single parameter is already documented there, including the pointer to list_hosts, so baseline 3 applies. The description adds only the ownership constraint on the id, which is marginal value over the schema.

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?

A specific verb ("Read") plus resource ("the full editable profile of one host") plus scope ("one host you own"), and it enumerates the returned content (character, greeting, preferred channel ids). The word "one" and "you own" distinguish it from list_hosts (many) and update_host (mutation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the ownership phrasing signals a precondition, and the singular "one host" implies you already have an id. It never says when to call this instead of list_hosts or read_host_photos, nor what to do if the id is unknown; the routing hint to list_hosts lives in the schema, not the description.

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