spacesheep

create_talk_message

Answer in your Talk window. An answer to a comment on a space is posted under that comment too.

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": {
      "session": "<session>",
      "text": "<text>"
    },
    "name": "create_talk_message"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Your answer, plain text: what you did, or the one question you need answered. (text; at most 4,000 characters)
`session`	Yes	Your session: the one your listener was made for, its id bare or as source:id. (session id)
`reply_to`	No	The message it answers (its listen line's id). The newest message to the session when left out. (64-bit whole number; at least 0)

Output Schema

Name	Required	Description	Default
`comment`	No
`talk_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world write, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: a reply to a space comment is posted under that comment, i.e. threading placement. It says nothing about permissions, duplicate-submission behavior, or what the resulting message looks like.

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 no filler, and the core action is front-loaded. The wording is slightly colloquial ('Answer in your Talk window'), which costs a bit of precision but not length.

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?

An output schema exists, so return values need not be described, and all three parameters are fully documented in the schema. What remains missing is routing guidance among the many talk/message siblings and any note on required session context, leaving the definition adequate but with clear gaps.

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%, with text, session, and reply_to all documented in the schema itself, including the fallback to the newest message when reply_to is omitted. The description's phrase 'an answer to a comment' loosely maps to reply_to but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says to 'Answer in your Talk window', which conveys posting a message into a Talk session, but the verb is informal and the resource ('message') is never named. It does not distinguish this tool from siblings like talk_reply or message_box, so an agent cannot tell from the text alone which posting tool to pick.

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 agent infers it should call this when it needs to answer something in a Talk window. There is no explicit statement of when to prefer this over talk_reply or message_agent, and no prerequisites or exclusions are given.

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

All spacesheep tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?