batman-mcp

Overview Schema Source Related Servers Discussions Admin

batman_register

Register a new user with username, email, and password in the Batman API to enable access to developer escalation and incident management tools.

Instructions

Registrar novo usuário na API Batman

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": {
      "username": "<username>",
      "email": "<email>",
      "password": "<password>"
    },
    "name": "batman_register"
  }
}

Input Schema

Name	Required	Description	Default
`email`	Yes
`password`	Yes
`username`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.1/5.0

Behavior1/5

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

No annotations are provided, and the description gives zero behavioral disclosure beyond the basic action. It doesn't mention side effects (e.g., creating a database record), required permissions, idempotency, or possible error conditions, leaving the agent without crucial safety information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which seems concise, but it is under-specified. It provides only a minimal phrase with no additional context or structure, which does not earn its place as a useful tool description.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 3 required parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain the registration flow, expected response, error scenarios, or any behavioral context, making it inadequate for an agent to use the tool safely and correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no parameter details. While parameter names (username, email, password) are self-explanatory, the description does not clarify required formats, constraints, or how they relate to the registration process, failing to compensate for the schema's lack of documentation.

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 'Registrar novo usuário na API Batman' clearly states the action (register) and resource (new user in the Batman API). It distinguishes from siblings like batman_login (login) and batman_create_developer (create developer) by using 'usuário' instead of 'developer', though the distinction is implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It only states what it does, with no mention of prerequisites, exclusions, or when to prefer other tools like batman_create_developer.

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

Deploy Server