simpleinout-mcp

simpleinout_create_my_status

Set or update your current status to check in or out, choosing from in, remote, busy, break, out, sick, or vacation. Include a comment or timestamp to backdate or schedule the change.

Instructions

Create (change) the current authenticated user's status — the core check-in/check-out action.

    API: POST /users/my/statuses

    Args:
        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": {
      "status": "<status>"
    },
    "name": "simpleinout_create_my_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes
`comment`	No
`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.6/5.0

Behavior4/5

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

With no annotations, the description carries the burden. It clearly states the mutation effect ('Create (change)') and the intended use as a check-in/check-out action. It also includes the API endpoint and argument semantics. Lacks explicit side-effect details (e.g., notifications, irreversibility), but the core behavior is well disclosed.

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?

The description is well-structured: a clear one-liner purpose, API endpoint, and bullet-like args. Every sentence earns its place; no wasted words. Scannable and informative.

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?

Given the tool's moderate complexity and absence of annotations, the description covers purpose, API, parameters, enums, and behavioral context. Output schema exists, so return values need no explanation. This is complete for an agent to select and invoke correctly.

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?

Schema description coverage is 0%, but the description fully compensates: it lists allowed status values, explains comment and created_at semantics including backdating/scheduling. This provides meaning far beyond the bare 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?

The description clearly states the action: 'Create (change) the current authenticated user's status' and identifies it as 'the core check-in/check-out action.' This specific verb+resource and scope fully distinguishes it from sibling tools like create_user_status (which targets other users).

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 provides clear context by specifying 'current authenticated user' and calling it the core check-in/check-out action. It does not explicitly mention alternative tools or when-not to use, but the scope is self-evident from the name and description, meeting the 'clear context, no exclusions' bar.

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

Deploy Server