Skip to main content
Glama
Sign In
MCP PR Workflow Server

MCP PR Workflow Server

by cindyylim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

notify_deployment_status

Send deployment success or failure notifications to Slack, including project name and optional details.

Instructions

Sends a formatted deployment status message (success/failure) to Slack.

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": {
      "project": "<project>",
      "status": "<status>"
    },
    "name": "notify_deployment_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes
detailsNo
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses the core action but lacks side-effect context such as formatting behavior, required Slack integration, or failure modes. The brief description does not add behavioral transparency beyond the literal action.

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, front-loaded with the verb, no redundant information. Ideal length for a simple tool description.

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?

The tool is simple, but with no annotations and no parameter descriptions, the overall context is thin. The description covers the primary purpose but fails to clarify parameter usage or how this relates to sibling tools, leaving moderate 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 description coverage is 0%, and the description only hints that status accepts success/failure (redundant with the enum). It does not explain the semantics of 'project' or 'details', leaving parameters underdocumented.

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 sends a formatted deployment status message to Slack, specifying the action (send), resource (deployment status), and recipient (Slack). This distinguishes it from the generic sibling send_slack_notification.

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 send_slack_notification. The description implies use for deployment status updates but does not state exclusions or prerequisites.

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