Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

search_tools

Read-onlyIdempotent

Search available LogicMonitor tools by keyword or category to find the right tool for a task, returning only tools visible under current server settings.

Instructions

Search the tools this server offers under its current settings by keyword, optionally within one category. Use it to find the tool for a task. It never names a tool the settings hide, so with writes off no write tool appears. Words such as 'the' and 'on' are ignored, plurals match singulars, and a query word that is a tool's full name ranks that tool first.

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": {
      "query": "<query>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default: 10)
queryYesSearch keywords (e.g., 'alert', 'device health', 'forecast')
categoryNoSearch only this category's tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.0.1
    • changedInput schema / properties / category / description
      Previous value: -"Filter to a specific category (e.g., 'alerts', 'ml_analysis')"New value: +"Search only this category's tools"
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "workflows",
      +  "universal_reference",
      +  "discovery",
      +  "devices",
      +  "alerts",
      +  "alert_rules",
      +  "sdts",
      +  "collectors",
      +  "networking",
      +  "datasources",
      +  "dashboards",
      +  "websites",
      +  "reports",
      +  "escalations",
      +  "integrations",
      +  "users",
      +  "topology",
      +  "audit",
      +  "usage",
      +  "cost",
      +  "logimodules",
      +  "netscans",
      +  "ops",
      +  "batchjobs",
      +  "imports",
      +  "ingestion",
      +  "logs",
      +  "otlp_metrics",
      +  "correlation",
      +  "traces",
      +  "ml_analysis",
      +  "session",
      +  "portals",
      +  "edwin",
      +  "terraform",
      +  "remediation",
      +  "actions"
      +]
  2. First observedv4.2.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: results are filtered by current server settings, hidden tools never appear (writes off means no write tools), and matching semantics include stop-word removal, plural/singular equivalence, and exact-name boosting. That tells the agent how to phrase a query and why a known tool might be absent, which the readOnly/idempotent hints do not convey.

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?

Four short sentences, front-loaded with the purpose, then usage, then matching behavior, with zero repetition. Every clause carries information an agent needs to construct a good query.

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?

Covers purpose, scoping, visibility rules, and matching semantics for a simple three-parameter tool. The one gap is the shape of the response (whether names, descriptions, or categories are returned), which matters more here because there is no output schema.

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 coverage is 100%, so baseline is 3; the description earns above that by defining query semantics (ignore "the"/"on", plural matching, exact-name ranking) and by framing category as an optional narrowing filter. It adds nothing for limit, but the schema already documents that default.

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?

States a specific verb and resource ("Search the tools this server offers") plus the scoping qualifier ("under its current settings by keyword"), which no sibling read tool shares. An agent can immediately tell this is the discovery/self-lookup tool rather than a data-fetching tool.

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?

Gives a clear use context: "Use it to find the tool for a task," and explains that category narrows scope. It stops short of naming when not to use it or naming an alternative path, so it sits at clear-context-but-no-exclusions.

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