Skip to main content
Glama
Sign In
batman-mcp

batman-mcp

by tadev77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batman_create_developer

Create a new developer profile in the Batman system to manage escalation and resolve incidents during sprints.

Instructions

Criar um novo desenvolvedor

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

Input Schema

NameRequiredDescriptionDefault
nameYes
priorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior1/5

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

With no annotations to cover safety or side effects, the description carries the full burden but reveals nothing about permissions, irreversibility, or response behavior. It merely says 'Criar um novo desenvolvedor' (Create a new developer), which gives no insight into what happens during the operation.

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

Conciseness3/5

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

The description is a single short sentence, which is concise and front-loaded, but it is under-specified for a tool with parameters and siblings. It is not overly verbose, but it sacrifices necessary detail, making it only minimally acceptable.

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 2 parameters, no output schema, and sibling tools that create other entity types, the description is far too bare. It does not explain prerequisites, return values, parameter meanings, or how this creation differs from others, leaving the agent to rely on guesswork.

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?

The schema has two parameters (name, priority) with 0% description coverage, and the description does not mention them at all. The agent receives no explanation of what 'name' or 'priority' mean, how they affect the creation, or any validation rules, so the description fails to compensate for the schema gap.

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 'Criar um novo desenvolvedor' clearly states the action (create) and resource (developer), making it distinguishable from siblings like 'update_developer' or 'delete_developer'. However, it lacks any additional specificity about the created entity's properties or context, so it doesn't fully earn a 5.

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?

There is no guidance on when to use this tool versus alternatives like 'batman_update_developer' or 'batman_get_developers'. The description only states the action without any contextual hints or exclusions, providing no usage direction beyond the obvious.

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

Deploy Server

Other Tools