Skip to main content
Glama
Sign In
batman-mcp

batman-mcp

by tadev77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batman_get_priority_details

Obtain detailed information about priority calculation for incident escalations, enabling clear understanding of how priority levels are assigned.

Instructions

Obter detalhes do cálculo de prioridade

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 provided, the description carries the full burden of disclosing behavioral traits. It only states a high-level action and offers no information about side effects, required permissions, return format, or potential errors. This is a significant transparency gap.

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 with no unnecessary words. It is front-loaded and easy to parse, making it highly concise. However, this conciseness comes at the cost of substantive content.

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?

The tool is simple (0 params, no annotations, no output schema), but the description still fails to explain what 'priority details' actually include or how the output can be used. An agent would have no idea what response to expect, making the description incomplete for real-world invocation.

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, so there is nothing for the description to elaborate on. The schema coverage is 100%, and with no params, the description's lack of parameter detail is not a deficiency. The baseline of 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Obter detalhes do cálculo de prioridade' is essentially a Portuguese translation of the tool name 'get_priority_details', providing no additional specifics. It identifies a verb and resource but does not distinguish from sibling tools like batman_get_history or batman_recalculate_priorities.

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 gives no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or exclusions, leaving the agent without any decision-making support.

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