simpleinout-mcp

simpleinout_create_user_status

Create or change another user's status in Simple In/Out, selecting from in, remote, busy, break, out, sick, or vacation. Requires permission to manage that user's status.

Instructions

Create (change) another user's status on their behalf. Requires the acting account to have permission to manage that user's status.

    API: POST /users/:id/statuses

    Args:
        user_id: Required. The user's ID to change the status for.
        status: Required. One of "in", "remote", "busy", "break", "out",
            "sick", "vacation".
        comment: Optional comment to attach to the status change.
        created_at: Optional timestamp to backdate/schedule the status change.

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": {
      "user_id": "<user_id>",
      "status": "<status>"
    },
    "name": "simpleinout_create_user_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes
`comment`	No
`user_id`	Yes
`created_at`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It mentions the permission requirement and that created_at can backdate/schedule the change, adding useful context. Yet it does not disclose whether the operation overwrites the existing status, triggers notifications, or has other side effects, leaving some behavioral ambiguity.

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?

The description is well-structured with an API line and a clean Args list, and every sentence adds value. The API endpoint may be technically useful but is not strictly necessary for an AI agent, making it slightly less concise than optimal.

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?

Given the tool's complexity and lack of annotations, the description covers purpose, permission, parameters, and allowed values. The presence of an output schema alleviates the need to describe return values. It does not address error scenarios or invalid input handling, but for a simple status-update tool it is reasonably complete.

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

Parameters5/5

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

The schema has zero parameter descriptions, and the description fully compensates by detailing each argument. It lists required fields, provides the exact allowed values for 'status' (in, remote, busy, break, out, sick, vacation), and explains the optional nature and purpose of 'comment' and 'created_at'.

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?

The description clearly states the tool's function: 'Create (change) another user's status on their behalf.' This distinguishes it from sibling tools like simpleinout_create_my_status, which would handle the acting user's own status. The verb 'Create' plus the resource 'status' makes the purpose unambiguous.

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 description clarifies that permission is required to manage the user's status, providing a prerequisite. It implies usage for changing another user's status, which differentiates it from tools like create_my_status. However, it does not explicitly state exclusions or mention alternative tools by name, so it falls slightly short of full guidance.

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

Deploy Server