Skip to main content
Glama
Sign In
transport-gzm

transport-gzm

by Wiktor102
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

alert_by_id

Retrieve detailed information for a specific service alert using its unique entity ID. Useful for inspecting individual alerts returned by the alerts tool.

Instructions

Get a single alert by entity id (e.g. from a previous alerts() result).

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

Input Schema

NameRequiredDescriptionDefault
alert_idYesEntity id of the alert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It explains the basic behavior (retrieve a single alert) but does not disclose potential errors, rate limits, or data freshness. For a simple read-only operation, this is adequate but not thorough.

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?

Single sentence with no unnecessary words. Front-loaded with the core action 'Get a single alert by entity id', making it immediately clear.

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

Completeness4/5

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

Given the simple nature (single parameter, no output schema), the description adequately explains what the tool does and how to obtain the input. No major gaps.

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?

Schema describes alert_id as 'Entity id of the alert.' The description adds that the id comes from a previous alerts() result, providing contextual meaning beyond the schema's definition.

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?

Description clearly states 'Get a single alert by entity id', specifying the verb 'Get', the resource 'alert', and that it's a single entity. It differentiates from sibling 'alerts' by noting the origin of the id from a previous alerts() result.

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

Usage Guidelines4/5

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

Description explicitly suggests when to use this tool: when you have an entity id from a previous alerts() result. This gives clear context, though it does not mention when not to use it or alternatives.

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