Skip to main content
Glama
Sign In
NetOps MCP Server

NetOps MCP Server

by drew-1618
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

query_incident_history

Retrieve past incident tickets to identify recurring failures, historical context, and open issues for network diagnostics.

Instructions

Queries past incident tickets to identify recurring failures, historical context, or open issues

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": "query_incident_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNo
targetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. 'Queries' implies a read-only operation and 'past incident tickets' conveys scope, but the description does not explicitly state that no tickets are modified, nor mention permissions, rate limits, or retention. It is adequate but not rich behavioral disclosure.

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 front-loaded sentence with no filler; it names the action, resource, and intended use cases immediately. There is no wasted text.

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 simple optional-parameter query with an output schema, the description supplies the core purpose. However, the unresolved semantics of status/target and the lack of explicit read-only confirmation leave gaps, making it a minimum-viable but not fully complete description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never addresses the three parameters. 'limit' is inferable from its name, but 'status' and especially 'target' are ambiguous—target of an incident, a host, or a service?—and no allowed values or examples are given.

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 opens with the specific verb 'Queries' and resource 'past incident tickets', then states concrete goals: recurring failures, historical context, and open issues. This clearly distinguishes it from sibling tools like create_incident_ticket, which writes, and network diagnostic tools such as run_ping and resolve_dns.

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?

It gives clear use cases: identifying recurring failures, historical context, or open issues. It does not explicitly name alternatives or exclusions, but none of the sibling tools performs incident-history lookup, so the usage context is reasonably clear.

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