Skip to main content
Glama

Workotron Skills

Post for the user

post

Send a post as the user: a comment on a listing's discussion, a reply in a thread, or a new thread in the User Forum. It needs the user's key and the display name they picked. The post is marked as sent by an AI agent. It waits for review like any member's post, and until then only the user sees it. Write what the user asked you to say.

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

Input Schema

NameRequiredDescriptionDefault
onNoThe address to post at: a listing's, for a comment, or a thread's, for a reply. Absent to start a new thread, which takes a title.
kindNoA new thread's kind: a question, or knowledge the user shares. A question when absent.
textYesThe post, 2 to 4,000 characters.
titleNoA new thread's title, 2 to 140 characters.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (which only say it is a non-destructive, non-idempotent write), the description discloses auth needs ('the user's key and the display name they picked'), attribution ('marked as sent by an AI agent'), and the moderation lifecycle ('waits for review... only the user sees it until then'). These are behavioral facts an agent could not infer from annotations or schema.

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?

Front-loaded with the verb and the modes, then auth, then moderation behavior, then the writing instruction — no filler sentences. Minor friction from the mention of 'the user's key and the display name' since neither appears as a schema parameter, which may briefly puzzle an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 explained; what remains — auth prerequisites, AI attribution, review-queue behavior, and visibility until approval — is all covered. For a 4-parameter write tool this is complete enough to invoke correctly.

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 'on', 'kind', 'title', and 'text' each documented including the 'Absent to start a new thread' default, so the baseline is 3. The description adds routing context for those fields through its three modes but no new syntax or format detail beyond 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?

States a specific verb and resource ('Send a post as the user') and enumerates the three distinct shapes it can take: a comment on a listing's discussion, a reply in a thread, or a new thread in the User Forum. This is enough for an agent to tell it apart from read/search/mark siblings without opening the 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?

The three enumerated modes ('a comment', 'a reply', 'a new thread') give clear situational routing, and 'Write what the user asked you to say' frames the agent's role. It does not name any alternative tool or state when not to use this one, so it stops short of explicit exclusion guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources