Skip to main content
Glama
Sign In
batman-mcp

batman-mcp

by tadev77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batman_get_developers

List developers in the Batman escalation system, optionally filtering by name or priority to identify available responders for incidents.

Instructions

Listar todos os desenvolvedores

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "batman_get_developers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
byPriorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It only says 'list all developers' without detailing how the 'name' and 'byPriority' parameters affect behavior, what the response looks like, or whether any permissions are required. This is insufficient for a tool with hidden behavioral nuances.

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 concise sentence with no fluff, but it is under-specified for the number of parameters. While it earns its place as a core statement, it lacks necessary details, making it not fully appropriately sized.

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

Completeness2/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 annotations, and no output schema, the description is incomplete. It does not explain how to use the parameters, what the return value is, or any edge cases. The description is minimally viable but fails to cover essential context for correct invocation.

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 does not mention either parameter ('name' or 'byPriority'). The description adds no meaning beyond the parameter names, leaving the agent without any clue about how to use them.

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: 'Listar todos os desenvolvedores' (List all developers). It uses a specific verb (list) and resource (developers) with explicit scope (all), and the plural form distinguishes it from the sibling tool 'batman_get_developer'.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this returns all developers while 'batman_get_developer' fetches a single one, nor does it explain any conditions for use.

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