Skip to main content
Glama
Sign In
appd-mcp

appd-mcp

by jagalliers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List AppDynamics health rules

appd_list_health_rules

List health rule summaries for an application, with option to fetch full rule definitions.

Instructions

List health rule summaries (id, name, enabled) for an application via the Alerting REST v1 API. Optionally fan out to fetch full rule definitions.

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": {
      "application": "<application>"
    },
    "name": "appd_list_health_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
applicationYes
expandDetailsNoWhen true, fan out per-rule GETs to fetch full health rule definitions (in addition to the list summaries). Default false to keep the call cheap.
maxDetailFanoutNoCap on per-rule detail fetches when expandDetails=true.

Output Schema

NameRequiredDescriptionDefault
summaryYes
evidenceNo
entitiesYes
timeRangeNo
sourceEndpointsYes
paginationNo
warningsYes
truncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / application / anyOf
      Previous value: -[
-  {
-    "description": "Application name",
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "description": "Application numeric id",
-    "exclusiveMinimum": 0,
-    "type": "integer"
-  }
-]New value: +[
+  {
+    "description": "Application name (1–255 chars)",
+    "maxLength": 255,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "description": "Application numeric id",
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  }
+]
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions the API and optional fan-out for full definitions, but omits details like error handling, performance impact, or required permissions. Partial transparency.

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?

Two concise sentences, front-loaded with purpose and optional behavior. No extraneous information.

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?

Output schema exists, so return values need not be described. Tool is simple with 3 params, but lacks context on usage scenarios, limitations, or error states. Adequate but with notable gaps.

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 coverage is 67% and the description does not explain parameters individually. It hints at expandDetails with 'optionally fan out' but does not describe application or maxDetailFanout. Minimal added value beyond schema.

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 the tool lists health rule summaries (id, name, enabled) for an application via the Alerting REST v1 API, and optionally fetches full rule definitions. This is specific and distinguishes from siblings that deal with violations or other configs.

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 guidance on when to use this tool versus alternatives like appd_get_health_rule_violations or appd_get_alerting_config. The description only states what it does, not when it is appropriate.

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