Skip to main content
Glama
Sign In
batman-mcp

batman-mcp

by tadev77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batman_get_current_batman

Identify the current Batman and Robin developers assigned to handle incident escalations during sprints. Retrieve the active escalation point of contact to know who is on duty.

Instructions

Obter o Batman e Robin atuais

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_current_batman"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description carries the full burden of behavioral disclosure. 'Obter' implies a read operation, but it does not disclose authentication requirements, return format, or side effects. This is minimal transparency beyond the verb itself.

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 a single short sentence, front-loaded with the action and resource, and contains no wasted words. It is appropriately sized for a tool with no parameters.

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?

For a no-parameter getter, the description is functional but thin. It lacks a statement of return value or domain context around 'current', and there is no output schema to compensate. However, sibling tool names provide some context about the system.

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?

The input schema has zero parameters, and the description adds no parameter information. With 0 parameters, a baseline of 4 is appropriate because there is nothing to document.

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 states 'Obter o Batman e Robin atuais', using the specific verb 'Obter' and naming the resource 'Batman e Robin atuais'. This clearly distinguishes it from sibling tools focused on developers, unavailabilities, or priorities, though it does not define what 'atuais' means in the domain.

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 usage guidance is provided. The description only says what the tool gets, not when to use it versus alternatives. There is no mention of exclusions or alternative tools, leaving the use case implied by the tool name.

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