Manufact

Back to submission

mf-mcp-server

mcp.hostedgraphite.com

Protocol: MCP 2025-11-25
Server version: 1.28.0
Supports: Tools
Resources
Prompts

Overall score

Last reviewed at Oct 14, 2026, 23:20:56 UTC

Server metadata

3 of 8 fields30/1003 / 10 pts

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

mf-mcp-server

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 1.28.0

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools, Resources, Prompts.

10/10Source

Protocol

Pass100/10020 / 20 pts

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 553ms

Source

Resources list responds

0 resource(s) returned

Source

Tools list returns results

35 tool(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues78/10023.4 / 30 pts

Tool definitions, annotations, and client compatibility.

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

All tools have descriptions

All tools have non-empty descriptions

Claude tools declare applicable behavior hints

35 Claude behavior annotation issue(s) found

How to fix: For Claude directory submission, declare the applicable annotations.readOnlyHint or annotations.destructiveHint value as a boolean on every tool.

errorClaude.ai

Source

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

All tools have OpenAI behavior hints

105 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

errorChatGPT

Source

All tools have a display title

35 tool(s) missing a display title: metric_search, busy_metrics, invalid_metrics, delete_metrics, create_alert, search_alerts, get_alert, update_alert, delete_alert, mute_alert, unmute_alert, get_alert_mute_status, mute_alerts, unmute_alerts, get_alert_history, create_notification_channel, search_notification_channels, get_notification_channel, update_notification_channel, delete_notification_channel, create_scheduled_mute, search_scheduled_mutes, get_scheduled_mute, update_scheduled_mute, delete_scheduled_mute, list_tags, search_tag_values, find_tagged_series, delete_tagged_series, create_dashboard, list_dashboards, get_dashboard, update_dashboard, delete_dashboard, render_graphite

How to fix: Set the top-level tool.title to a short human-readable label (for example, "Search catalog"). Claude directory submission requires tool titles; annotations.title remains accepted only as a legacy fallback.

errorClaude.ai

Source

Tool names use valid characters

All tool names use valid characters

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

ChatGPT tool names are unique

All tool names are unique

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

MCP Apps

Not applicable-Optional

App resources, metadata, and rendering requirements.

Declared domains respond

No view resources found — view checks skipped

All discovered view resources were inspected

No view resources found — view checks skipped

Source

View resource metadata complete

No view resources found — view checks skipped

Source

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

View resource envelope is valid

No view resources found — view checks skipped

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

Tool invocation metadata present

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

Tool documentation quality

35 tools reviewed34/10013.6 / 40 pts

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

metric_searchTitles 48Descriptions 63Inputs 0Annotations 0Outputs 030/100

Title48/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description63/100

Search account metrics by Graphite-style pattern (e.g. foo.bar.*).

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

pattern

Not provided

Missing description. Explain what this value means and how to supply it.

only_updated_after

Not provided

Missing description. Explain what this value means and how to supply it.

only_updated_before

Not provided

Missing description. Explain what this value means and how to supply it.

page

Not provided

Missing description. Explain what this value means and how to supply it.

with_times

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "metric_search",
  "description": "Search account metrics by Graphite-style pattern (e.g. foo.bar.*).",
  "inputSchema": {
    "type": "object",
    "title": "metric_searchArguments",
    "required": [
      "pattern"
    ],
    "properties": {
      "page": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Page",
        "default": null
      },
      "pattern": {
        "type": "string",
        "title": "Pattern"
      },
      "with_times": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "With Times",
        "default": null
      },
      "only_updated_after": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Only Updated After",
        "default": null
      },
      "only_updated_before": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Only Updated Before",
        "default": null
      }
    }
  }
}

busy_metricsTitles 55Descriptions 75Inputs 100Annotations 0Outputs 061/100

Title55/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description75/100

Return the busiest metric in the account and its rate-limit percentage.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "busy_metrics",
  "description": "Return the busiest metric in the account and its rate-limit percentage.",
  "inputSchema": {
    "type": "object",
    "title": "busy_metricsArguments",
    "properties": {}
  }
}

invalid_metricsTitles 38Descriptions 70Inputs 100Annotations 0Outputs 055/100

Title38/100

Not provided

Shorten the title to an action and subject; move usage details into the description.

Description70/100

Return invalid metrics rejected by Hosted Graphite parsers.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "invalid_metrics",
  "description": "Return invalid metrics rejected by Hosted Graphite parsers.",
  "inputSchema": {
    "type": "object",
    "title": "invalid_metricsArguments",
    "properties": {}
  }
}

delete_metricsTitles 50Descriptions 73Inputs 0Annotations 0Outputs 033/100

Title50/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description73/100

Delete all metrics matching a Graphite-style pattern (e.g. test.*).

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

pattern

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_metrics",
  "description": "Delete all metrics matching a Graphite-style pattern (e.g. test.*).",
  "inputSchema": {
    "type": "object",
    "title": "delete_metricsArguments",
    "required": [
      "pattern"
    ],
    "properties": {
      "pattern": {
        "type": "string",
        "title": "Pattern"
      }
    }
  }
}

create_alertTitles 53Descriptions 62Inputs 0Annotations 0Outputs 031/100

Title53/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description62/100

Create a Hosted Graphite alert (supports composite alerts via additional_criteria and expression).

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 10 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

Not provided

Missing description. Explain what this value means and how to supply it.

metric

Not provided

Missing description. Explain what this value means and how to supply it.

alert_criteria

Not provided

Missing description. Explain what this value means and how to supply it.

additional_criteria

Not provided

Missing description. Explain what this value means and how to supply it.

expression

Not provided

Missing description. Explain what this value means and how to supply it.

scheduled_mutes

Not provided

Missing description. Explain what this value means and how to supply it.

notification_channels

Not provided

Missing description. Explain what this value means and how to supply it.

notification_type

Not provided

Missing description. Explain what this value means and how to supply it.

info

Not provided

Missing description. Explain what this value means and how to supply it.

on_query_failure

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_alert",
  "description": "Create a Hosted Graphite alert (supports composite alerts via additional_criteria and expression).",
  "inputSchema": {
    "type": "object",
    "title": "create_alertArguments",
    "required": [
      "name",
      "metric",
      "alert_criteria"
    ],
    "properties": {
      "info": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Info",
        "default": null
      },
      "name": {
        "type": "string",
        "title": "Name"
      },
      "metric": {
        "type": "string",
        "title": "Metric"
      },
      "expression": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Expression",
        "default": null
      },
      "alert_criteria": {
        "type": "object",
        "title": "Alert Criteria",
        "additionalProperties": true
      },
      "scheduled_mutes": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Scheduled Mutes",
        "default": null
      },
      "on_query_failure": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "On Query Failure",
        "default": null
      },
      "notification_type": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "array",
            "items": {}
          },
          {
            "type": "null"
          }
        ],
        "title": "Notification Type",
        "default": null
      },
      "additional_criteria": {
        "anyOf": [
          {
            "type": "object",
            "additionalProperties": true
          },
          {
            "type": "null"
          }
        ],
        "title": "Additional Criteria",
        "default": null
      },
      "notification_channels": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Notification Channels",
        "default": null
      }
    }
  }
}

search_alertsTitles 53Descriptions 65Inputs 0Annotations 0Outputs 031/100

Title53/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description65/100

Search alerts by name, id, or free-text search string.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

names

Not provided

Missing description. Explain what this value means and how to supply it.

ids

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

page

Not provided

Missing description. Explain what this value means and how to supply it.

max_results

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_alerts",
  "description": "Search alerts by name, id, or free-text search string.",
  "inputSchema": {
    "type": "object",
    "title": "search_alertsArguments",
    "properties": {
      "ids": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Ids",
        "default": null
      },
      "page": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Page",
        "default": null
      },
      "names": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Names",
        "default": null
      },
      "search": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Search",
        "default": null
      },
      "max_results": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Max Results",
        "default": null
      }
    }
  }
}

get_alertTitles 55Descriptions 72Inputs 0Annotations 0Outputs 034/100

Title55/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description72/100

Get details for a single alert by id.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

alert_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_alert",
  "description": "Get details for a single alert by id.",
  "inputSchema": {
    "type": "object",
    "title": "get_alertArguments",
    "required": [
      "alert_id"
    ],
    "properties": {
      "alert_id": {
        "type": "string",
        "title": "Alert Id"
      }
    }
  }
}

update_alertTitles 58Descriptions 73Inputs 0Annotations 0Outputs 035/100

Title58/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description73/100

Update one or more fields on an alert. Only specified fields are changed.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

alert_id

Not provided

Missing description. Explain what this value means and how to supply it.

updates

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_alert",
  "description": "Update one or more fields on an alert. Only specified fields are changed.",
  "inputSchema": {
    "type": "object",
    "title": "update_alertArguments",
    "required": [
      "alert_id",
      "updates"
    ],
    "properties": {
      "updates": {
        "type": "object",
        "title": "Updates",
        "additionalProperties": true
      },
      "alert_id": {
        "type": "string",
        "title": "Alert Id"
      }
    }
  }
}

delete_alertTitles 69Descriptions 71Inputs 0Annotations 0Outputs 037/100

Title69/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

Delete an alert by id.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

alert_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_alert",
  "description": "Delete an alert by id.",
  "inputSchema": {
    "type": "object",
    "title": "delete_alertArguments",
    "required": [
      "alert_id"
    ],
    "properties": {
      "alert_id": {
        "type": "string",
        "title": "Alert Id"
      }
    }
  }
}

mute_alertTitles 46Descriptions 64Inputs 0Annotations 0Outputs 029/100

Title46/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description64/100

Mute an alert for the given number of minutes.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

alert_id

Not provided

Missing description. Explain what this value means and how to supply it.

duration

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "mute_alert",
  "description": "Mute an alert for the given number of minutes.",
  "inputSchema": {
    "type": "object",
    "title": "mute_alertArguments",
    "required": [
      "alert_id",
      "duration"
    ],
    "properties": {
      "alert_id": {
        "type": "string",
        "title": "Alert Id"
      },
      "duration": {
        "type": "integer",
        "title": "Duration"
      }
    }
  }
}

unmute_alertTitles 60Descriptions 68Inputs 0Annotations 0Outputs 034/100

Title60/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description68/100

Unmute an alert by id.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

alert_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "unmute_alert",
  "description": "Unmute an alert by id.",
  "inputSchema": {
    "type": "object",
    "title": "unmute_alertArguments",
    "required": [
      "alert_id"
    ],
    "properties": {
      "alert_id": {
        "type": "string",
        "title": "Alert Id"
      }
    }
  }
}

get_alert_mute_statusTitles 58Descriptions 68Inputs 0Annotations 0Outputs 034/100

Title58/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description68/100

Get mute status and scheduled mutes for an alert.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

alert_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_alert_mute_status",
  "description": "Get mute status and scheduled mutes for an alert.",
  "inputSchema": {
    "type": "object",
    "title": "get_alert_mute_statusArguments",
    "required": [
      "alert_id"
    ],
    "properties": {
      "alert_id": {
        "type": "string",
        "title": "Alert Id"
      }
    }
  }
}

mute_alertsTitles 41Descriptions 72Inputs 0Annotations 0Outputs 030/100

Title41/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description72/100

Mute multiple alerts by id list or search string. Mutes all alerts if both are omitted.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

duration

Not provided

Missing description. Explain what this value means and how to supply it.

ids

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "mute_alerts",
  "description": "Mute multiple alerts by id list or search string. Mutes all alerts if both are omitted.",
  "inputSchema": {
    "type": "object",
    "title": "mute_alertsArguments",
    "required": [
      "duration"
    ],
    "properties": {
      "ids": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Ids",
        "default": null
      },
      "search": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Search",
        "default": null
      },
      "duration": {
        "type": "integer",
        "title": "Duration"
      }
    }
  }
}

unmute_alertsTitles 38Descriptions 78Inputs 0Annotations 0Outputs 031/100

Title38/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description78/100

Unmute multiple alerts by id list or search string. Unmutes all alerts if both are omitted.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

ids

Not provided

Missing description. Explain what this value means and how to supply it.

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "unmute_alerts",
  "description": "Unmute multiple alerts by id list or search string. Unmutes all alerts if both are omitted.",
  "inputSchema": {
    "type": "object",
    "title": "unmute_alertsArguments",
    "properties": {
      "ids": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Ids",
        "default": null
      },
      "search": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Search",
        "default": null
      }
    }
  }
}

get_alert_historyTitles 57Descriptions 66Inputs 0Annotations 0Outputs 033/100

Title57/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description66/100

Get alert trigger/recovery history, optionally filtered by alert id and other fields.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

alert_ids

Not provided

Missing description. Explain what this value means and how to supply it.

days

Not provided

Missing description. Explain what this value means and how to supply it.

status

Not provided

Missing description. Explain what this value means and how to supply it.

value

Not provided

Missing description. Explain what this value means and how to supply it.

time

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_alert_history",
  "description": "Get alert trigger/recovery history, optionally filtered by alert id and other fields.",
  "inputSchema": {
    "type": "object",
    "title": "get_alert_historyArguments",
    "properties": {
      "days": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Days",
        "default": null
      },
      "time": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Time",
        "default": null
      },
      "value": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Value",
        "default": null
      },
      "status": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Status",
        "default": null
      },
      "alert_ids": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Alert Ids",
        "default": null
      }
    }
  }
}

create_notification_channelTitles 49Descriptions 61Inputs 0Annotations 0Outputs 029/100

Title49/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description61/100

Create a notification channel (email, slack, pagerduty, webhook, victorops, opsgenie).

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

type

Not provided

Missing description. Explain what this value means and how to supply it.

description

Not provided

Missing description. Explain what this value means and how to supply it.

destination

Not provided

Missing description. Explain what this value means and how to supply it.

auto_resolve

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_notification_channel",
  "description": "Create a notification channel (email, slack, pagerduty, webhook, victorops, opsgenie).",
  "inputSchema": {
    "type": "object",
    "title": "create_notification_channelArguments",
    "required": [
      "type",
      "description",
      "destination"
    ],
    "properties": {
      "type": {
        "type": "string",
        "title": "Type"
      },
      "description": {
        "type": "string",
        "title": "Description"
      },
      "destination": {
        "type": "string",
        "title": "Destination"
      },
      "auto_resolve": {
        "anyOf": [
          {
            "type": "boolean"
          },
          {
            "type": "null"
          }
        ],
        "title": "Auto Resolve",
        "default": null
      }
    }
  }
}

search_notification_channelsTitles 41Descriptions 83Inputs 0Annotations 0Outputs 033/100

Title41/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description83/100

Search notification channels by type, description, or id. Returns all if filters are omitted.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

types

Not provided

Missing description. Explain what this value means and how to supply it.

descriptions

Not provided

Missing description. Explain what this value means and how to supply it.

ids

Not provided

Missing description. Explain what this value means and how to supply it.

page

Not provided

Missing description. Explain what this value means and how to supply it.

max_results

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_notification_channels",
  "description": "Search notification channels by type, description, or id. Returns all if filters are omitted.",
  "inputSchema": {
    "type": "object",
    "title": "search_notification_channelsArguments",
    "properties": {
      "ids": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Ids",
        "default": null
      },
      "page": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Page",
        "default": null
      },
      "types": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Types",
        "default": null
      },
      "max_results": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Max Results",
        "default": null
      },
      "descriptions": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Descriptions",
        "default": null
      }
    }
  }
}

get_notification_channelTitles 50Descriptions 71Inputs 0Annotations 0Outputs 032/100

Title50/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

Get details for a single notification channel by id.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

notification_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_notification_channel",
  "description": "Get details for a single notification channel by id.",
  "inputSchema": {
    "type": "object",
    "title": "get_notification_channelArguments",
    "required": [
      "notification_id"
    ],
    "properties": {
      "notification_id": {
        "type": "string",
        "title": "Notification Id"
      }
    }
  }
}

update_notification_channelTitles 60Descriptions 67Inputs 0Annotations 0Outputs 034/100

Title60/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description67/100

Update one or more fields on a notification channel. Only specified fields are changed.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

notification_id

Not provided

Missing description. Explain what this value means and how to supply it.

updates

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_notification_channel",
  "description": "Update one or more fields on a notification channel. Only specified fields are changed.",
  "inputSchema": {
    "type": "object",
    "title": "update_notification_channelArguments",
    "required": [
      "notification_id",
      "updates"
    ],
    "properties": {
      "updates": {
        "type": "object",
        "title": "Updates",
        "additionalProperties": true
      },
      "notification_id": {
        "type": "string",
        "title": "Notification Id"
      }
    }
  }
}

delete_notification_channelTitles 55Descriptions 72Inputs 0Annotations 0Outputs 034/100

Title55/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description72/100

Delete a notification channel by id.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

notification_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_notification_channel",
  "description": "Delete a notification channel by id.",
  "inputSchema": {
    "type": "object",
    "title": "delete_notification_channelArguments",
    "required": [
      "notification_id"
    ],
    "properties": {
      "notification_id": {
        "type": "string",
        "title": "Notification Id"
      }
    }
  }
}

create_scheduled_muteTitles 61Descriptions 64Inputs 0Annotations 0Outputs 033/100

Title61/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description64/100

Create a scheduled mute. repeat days are mon–sun; omit for a one-time mute.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

name

Not provided

Missing description. Explain what this value means and how to supply it.

start_time

Not provided

Missing description. Explain what this value means and how to supply it.

duration

Not provided

Missing description. Explain what this value means and how to supply it.

timezone

Not provided

Missing description. Explain what this value means and how to supply it.

repeat

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_scheduled_mute",
  "description": "Create a scheduled mute. repeat days are mon–sun; omit for a one-time mute.",
  "inputSchema": {
    "type": "object",
    "title": "create_scheduled_muteArguments",
    "required": [
      "name",
      "start_time",
      "duration"
    ],
    "properties": {
      "name": {
        "type": "string",
        "title": "Name"
      },
      "repeat": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Repeat",
        "default": null
      },
      "duration": {
        "type": "integer",
        "title": "Duration"
      },
      "timezone": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Timezone",
        "default": null
      },
      "start_time": {
        "type": "string",
        "title": "Start Time"
      }
    }
  }
}

search_scheduled_mutesTitles 45Descriptions 67Inputs 0Annotations 0Outputs 030/100

Title45/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description67/100

Search scheduled mutes by name, id, duration, start_time, timezone, or repeat day.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

names

Not provided

Missing description. Explain what this value means and how to supply it.

ids

Not provided

Missing description. Explain what this value means and how to supply it.

durations

Not provided

Missing description. Explain what this value means and how to supply it.

start_times

Not provided

Missing description. Explain what this value means and how to supply it.

timezones

Not provided

Missing description. Explain what this value means and how to supply it.

repeat

Not provided

Missing description. Explain what this value means and how to supply it.

page

Not provided

Missing description. Explain what this value means and how to supply it.

max_results

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_scheduled_mutes",
  "description": "Search scheduled mutes by name, id, duration, start_time, timezone, or repeat day.",
  "inputSchema": {
    "type": "object",
    "title": "search_scheduled_mutesArguments",
    "properties": {
      "ids": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Ids",
        "default": null
      },
      "page": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Page",
        "default": null
      },
      "names": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Names",
        "default": null
      },
      "repeat": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Repeat",
        "default": null
      },
      "durations": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "integer"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Durations",
        "default": null
      },
      "timezones": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Timezones",
        "default": null
      },
      "max_results": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Max Results",
        "default": null
      },
      "start_times": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Start Times",
        "default": null
      }
    }
  }
}

get_scheduled_muteTitles 54Descriptions 71Inputs 0Annotations 0Outputs 033/100

Title54/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

Get details for a single scheduled mute by id.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

schedule_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_scheduled_mute",
  "description": "Get details for a single scheduled mute by id.",
  "inputSchema": {
    "type": "object",
    "title": "get_scheduled_muteArguments",
    "required": [
      "schedule_id"
    ],
    "properties": {
      "schedule_id": {
        "type": "string",
        "title": "Schedule Id"
      }
    }
  }
}

update_scheduled_muteTitles 60Descriptions 66Inputs 0Annotations 0Outputs 034/100

Title60/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description66/100

Update one or more fields on a scheduled mute. Only specified fields are changed.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

schedule_id

Not provided

Missing description. Explain what this value means and how to supply it.

updates

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_scheduled_mute",
  "description": "Update one or more fields on a scheduled mute. Only specified fields are changed.",
  "inputSchema": {
    "type": "object",
    "title": "update_scheduled_muteArguments",
    "required": [
      "schedule_id",
      "updates"
    ],
    "properties": {
      "updates": {
        "type": "object",
        "title": "Updates",
        "additionalProperties": true
      },
      "schedule_id": {
        "type": "string",
        "title": "Schedule Id"
      }
    }
  }
}

delete_scheduled_muteTitles 49Descriptions 69Inputs 0Annotations 0Outputs 031/100

Title49/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description69/100

Delete a scheduled mute by id.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

schedule_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_scheduled_mute",
  "description": "Delete a scheduled mute by id.",
  "inputSchema": {
    "type": "object",
    "title": "delete_scheduled_muteArguments",
    "required": [
      "schedule_id"
    ],
    "properties": {
      "schedule_id": {
        "type": "string",
        "title": "Schedule Id"
      }
    }
  }
}

list_tagsTitles 46Descriptions 71Inputs 0Annotations 0Outputs 031/100

Title46/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

List all tag names in the account. Optionally filter by name and limit results.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

filter

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_tags",
  "description": "List all tag names in the account. Optionally filter by name and limit results.",
  "inputSchema": {
    "type": "object",
    "title": "list_tagsArguments",
    "properties": {
      "limit": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Limit",
        "default": null
      },
      "filter": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Filter",
        "default": null
      }
    }
  }
}

search_tag_valuesTitles 49Descriptions 67Inputs 0Annotations 0Outputs 031/100

Title49/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description67/100

Search values for a tag name (e.g. host with filter=prod-00*).

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

tag_name

Not provided

Missing description. Explain what this value means and how to supply it.

filter

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "search_tag_values",
  "description": "Search values for a tag name (e.g. host with filter=prod-00*).",
  "inputSchema": {
    "type": "object",
    "title": "search_tag_valuesArguments",
    "required": [
      "tag_name"
    ],
    "properties": {
      "limit": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Limit",
        "default": null
      },
      "filter": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Filter",
        "default": null
      },
      "tag_name": {
        "type": "string",
        "title": "Tag Name"
      }
    }
  }
}

find_tagged_seriesTitles 35Descriptions 64Inputs 0Annotations 0Outputs 026/100

Title35/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description64/100

Find tagged series matching tag expressions (e.g. cluster=prod).

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

exprs

Not provided

Missing description. Explain what this value means and how to supply it.

filter

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "find_tagged_series",
  "description": "Find tagged series matching tag expressions (e.g. cluster=prod).",
  "inputSchema": {
    "type": "object",
    "title": "find_tagged_seriesArguments",
    "properties": {
      "exprs": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "title": "Exprs",
        "default": null
      },
      "limit": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "title": "Limit",
        "default": null
      },
      "filter": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "Filter",
        "default": null
      }
    }
  }
}

delete_tagged_seriesTitles 44Descriptions 66Inputs 0Annotations 0Outputs 029/100

Title44/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description66/100

Delete tagged series by path (e.g. foo.bar;tag1=val1;tag2=val2).

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

series

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_tagged_series",
  "description": "Delete tagged series by path (e.g. foo.bar;tag1=val1;tag2=val2).",
  "inputSchema": {
    "type": "object",
    "title": "delete_tagged_seriesArguments",
    "required": [
      "series"
    ],
    "properties": {
      "series": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "title": "Series"
      }
    }
  }
}

create_dashboardTitles 56Descriptions 62Inputs 0Annotations 0Outputs 031/100

Title56/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description62/100

Create a new Grafana dashboard.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

dashboard

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_dashboard",
  "description": "Create a new Grafana dashboard.",
  "inputSchema": {
    "type": "object",
    "title": "create_dashboardArguments",
    "required": [
      "dashboard"
    ],
    "properties": {
      "dashboard": {
        "type": "object",
        "title": "Dashboard",
        "additionalProperties": true
      }
    }
  }
}

list_dashboardsTitles 46Descriptions 62Inputs 100Annotations 0Outputs 055/100

Title46/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description62/100

List Grafana dashboards.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_dashboards",
  "description": "List Grafana dashboards.",
  "inputSchema": {
    "type": "object",
    "title": "list_dashboardsArguments",
    "properties": {}
  }
}

get_dashboardTitles 58Descriptions 72Inputs 0Annotations 0Outputs 035/100

Title58/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description72/100

Get a single Grafana dashboard by uid.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

uid

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_dashboard",
  "description": "Get a single Grafana dashboard by uid.",
  "inputSchema": {
    "type": "object",
    "title": "get_dashboardArguments",
    "required": [
      "uid"
    ],
    "properties": {
      "uid": {
        "type": "string",
        "title": "Uid"
      }
    }
  }
}

update_dashboardTitles 57Descriptions 69Inputs 0Annotations 0Outputs 034/100

Title57/100

Not provided

Shorten the title to an action and subject; move usage details into the description.

Description69/100

Update an existing Grafana dashboard by uid.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

uid

Not provided

Missing description. Explain what this value means and how to supply it.

dashboard

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "update_dashboard",
  "description": "Update an existing Grafana dashboard by uid.",
  "inputSchema": {
    "type": "object",
    "title": "update_dashboardArguments",
    "required": [
      "uid",
      "dashboard"
    ],
    "properties": {
      "uid": {
        "type": "string",
        "title": "Uid"
      },
      "dashboard": {
        "type": "object",
        "title": "Dashboard",
        "additionalProperties": true
      }
    }
  }
}

delete_dashboardTitles 51Descriptions 73Inputs 0Annotations 0Outputs 033/100

Title51/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description73/100

Delete a Grafana dashboard by uid.

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

uid

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "delete_dashboard",
  "description": "Delete a Grafana dashboard by uid.",
  "inputSchema": {
    "type": "object",
    "title": "delete_dashboardArguments",
    "required": [
      "uid"
    ],
    "properties": {
      "uid": {
        "type": "string",
        "title": "Uid"
      }
    }
  }
}

render_graphiteTitles 53Descriptions 63Inputs 0Annotations 0Outputs 031/100

Title53/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description63/100

Query Graphite render API for metric data or graph images. Uses the MCP token against /mcp/graphite/render on the API host.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

targets

Not provided

Missing description. Explain what this value means and how to supply it.

from_time

Not provided

Missing description. Explain what this value means and how to supply it.

to_time

Not provided

Missing description. Explain what this value means and how to supply it.

format

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "render_graphite",
  "description": "Query Graphite render API for metric data or graph images.\n\n    Uses the MCP token against /mcp/graphite/render on the API host.\n    ",
  "inputSchema": {
    "type": "object",
    "title": "render_graphiteArguments",
    "required": [
      "targets"
    ],
    "properties": {
      "format": {
        "enum": [
          "json",
          "csv",
          "raw",
          "png",
          "svg"
        ],
        "type": "string",
        "title": "Format",
        "default": "json"
      },
      "targets": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "title": "Targets"
      },
      "to_time": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "To Time",
        "default": null
      },
      "from_time": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "title": "From Time",
        "default": null
      }
    }
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01List Grafana dashboards
02Search alertsSearch alerts by name, id, or free-text search string.
03List all tag names in the account
04Search tag valuesSearch values for a tag name (e.g.
05Get a single Grafana dashboard by uid

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

Overview

Category: Developer tools

FAQ

mf-mcp-server setup, tools, quality score, publishing readiness, and alternatives.

How do I add mf-mcp-server to Claude, ChatGPT, or Cursor?

Add mf-mcp-server to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.hostedgraphite.com/.

Is mf-mcp-server MCP ready for ChatGPT and Claude?

As of October 14, 2026, mf-mcp-server scores 82/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and does not yet meet Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is mf-mcp-server's MCP tool documentation?

As of October 14, 2026, mf-mcp-server scores 34/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 35 of 35 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What are the best alternatives to mf-mcp-server?

As of October 15, 2026, alternatives to mf-mcp-server in developer-tools on the Manufact MCP catalog include Held at the Gate, AgentMail, Manufact Cloud, Authdog, and GitCafe.

How can mf-mcp-server improve its MCP documentation?

find_tagged_series is the lowest-scoring reviewed tool at 26/100. 0 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…