Skip to main content
Glama
Sign In
Joxo

Joxo

Official
by JoxoAI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tell_people

Post team-chat updates on completed work, results, or blockers using summary/details or plain text, and send direct messages to the owner.

Instructions

Post to the team chat people read on their phones: what you did with their idea (name the task or PR), a result, a heads-up. summary plus details, or text. to: "owner" is a direct message only this computer's owner reads.

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

Input Schema

NameRequiredDescriptionDefault
toNo
textNoPlain text, instead of summary.
threadNo
detailsNoThe rest: evidence, steps.
summaryNoOutcome first, in plain words; no internals (files, tools) unless they are the point; anything longer goes in details.
in_reply_toNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the write/external-visibility profile is covered. The description usefully adds delivery context (people read it on their phones) and DM visibility semantics for to:"owner", but says nothing about persistence, editability, rate limits, or whether the whole team sees the post.

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?

Three short sentences, front-loaded with the channel and payload form before the DM caveat; there is little filler. The phrase 'a heads-up' is slightly vague but costs almost nothing.

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?

For a 6-parameter tool with a nested summary object and no output schema, the description covers the main composition paths but leaves thread/in_reply_to unexplained and does not indicate what posting returns or whether it is fire-and-forget. Adequate but with visible 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?

With 50% schema coverage, the description compensates partially: it explains that summary+details and text are alternative composition modes and what to:"owner" does. However, thread and in_reply_to are undocumented in both places, and the summary object's internal guidance lives in the schema rather than the description.

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 gives a concrete verb and channel ('Post to the team chat people read on their phones') and specifies the payload shapes ('summary plus details, or text') plus the DM variant for to:"owner". An agent can tell it is a progress/notification poster, though it never names the nearby siblings send_message, ask_people, or publish_handoff to disambiguate.

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 implied rather than stated: it suggests reporting what you did with someone's idea, a result, or a heads-up, and clarifies that to:"owner" is a private DM. There is no explicit when-to-use-this-vs-send_message/ask_people/publish_handoff guidance, which matters given three plausibly overlapping messaging siblings.

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