Skip to main content
Glama

thanaton_manage_deploy_hooks

List, create, or delete Git/CI-CD deployment webhook triggers to automate autonomous build execution for a project.

Instructions

List, create, or delete Git / CI/CD deployment webhook triggers for autonomous build execution.

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_id": "<project_id>",
      "action": "<action>"
    },
    "name": "thanaton_manage_deploy_hooks"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoHook label (for create, e.g. GitHub Main Push)
actionYesAction to perform
branchNoTarget branch (for create, default: main)
hook_idNoHook ID (required for delete)
project_idYesTarget project ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses very little beyond the fact that hooks relate to 'autonomous build execution'. It does not say whether deletion is irreversible, whether creating a hook triggers an immediate build, what authorization is required, or what a list returns. For a mixed read/write tool, that is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the action set first and the resource second, so an agent can parse it in one pass. The trailing phrase 'for autonomous build execution' is slightly vague filler but is small enough not to hurt.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-parameter, multi-action mutation tool with no annotations and no output schema, so the description is the only behavioral source. It omits irreversibility of delete, prerequisites for create, and any sense of what a list operation yields, leaving real gaps for the agent.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including the action enum, hook_id, and branch defaults is already documented in the schema. The description adds no format, constraint, or conditional detail beyond it, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verbs (list, create, delete) and a concrete resource (Git / CI/CD deployment webhook triggers), which is enough for an agent to distinguish this from thanaton_manage_crons or thanaton_deploy_code. It stops short of naming the adjacent tool it should not be confused with, but the purpose itself is unambiguous.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as thanaton_deploy_code or thanaton_manage_crons. The agent must infer from the enum that 'create' is for setup and 'delete' for teardown, with nothing about ordering, permissions, or side effects.

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