simpleinout-mcp

simpleinout_get_user

Retrieve a specific user's information by passing their user ID. Solves the need to access user details directly from the Simple In/Out system.

Instructions

Retrieve a specific user.

    API: GET /users/:id

    Args:
        user_id: Required. The user's ID.

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>"
    },
    "name": "simpleinout_get_user"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the API endpoint and parameter, but does not mention potential errors (e.g., not found), authentication requirements, or any side effects. The behavior is largely opaque.

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 concise and well-structured: a one-sentence purpose, the API reference, and the argument definition. No unnecessary words, and it earns its place.

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?

Given the tool's simplicity and the presence of an output schema, the description suffices for basic usage. However, it misses the opportunity to clarify differentiation from sibling tools like get_current_user, which could cause confusion during tool selection.

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

Parameters4/5

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

Although schema description coverage is 0%, the description adds meaningful semantic context for the single parameter: 'user_id: Required. The user's ID.' This clarifies the purpose of the parameter beyond the schema's bare type declaration.

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 'Retrieve a specific user' with a direct API endpoint, making the tool's purpose unambiguous. It distinguishes itself from list_users by emphasizing 'specific user' and from get_current_user by implying a user ID is provided.

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?

The description implies usage (provide user_id to get a specific user) but does not explicitly discuss when to use this tool over alternatives like get_current_user or list_users. No exclusions or alternative tool names are mentioned.

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

Deploy Server