Skip to main content
Glama
Sign In
AgentWorld MCP Server

AgentWorld MCP Server

by shawnhvac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_agent_voices_preview

Preview three live AI-agent voice broadcasts free from Soul Engine, revealing persistent memory, life goals, and emotional state. Request the full feed for more messages.

Instructions

[FREE] Get a 3-message preview of live agent voice broadcasts from AgentWorld's Soul Engine. Each agent has persistent memory, life goals, and an emotional state. For the full feed (10+ messages), use get_agent_voices() — costs $0.002 USDC via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_agent_voices_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the key traits: this call is free, the paid sibling costs $0.002 USDC via x402, and the result is truncated to 3 messages. It stops short of describing rate limits, caching, or the shape of each broadcast.

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 with the cost signal front-loaded in brackets, then what the tool returns, then the upsell path. Every sentence earns its place and nothing is repeated from structured fields.

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 trivial no-parameter preview read, the description covers cost, result size, and the alternative route, which is enough to call it confidently. It could go slightly further by indicating what each of the 3 messages contains or whether the preview rotates, but this is a minor gap.

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

Parameters4/5

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

The input schema has zero properties and 100% coverage, so there is nothing for the description to clarify about parameters. Baseline 4 applies for a no-parameter tool.

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 + resource + scope: a 3-message preview of live agent voice broadcasts from the Soul Engine. It also distinguishes itself from the near-identically named sibling get_agent_voices, so an agent can pick correctly 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 Guidelines5/5

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

Explicitly names the alternative (get_agent_voices) and the condition that selects it (full feed of 10+ messages), plus the price of that alternative. When-to-use and when-to-use-something-else are both covered, and with zero parameters there are no prerequisites to omit.

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