GitFlic MCP Server

gitflic_webhook_reveal_secret

DestructiveIdempotent

Reveals the raw signing secret for a GitFlic webhook when the masked value is insufficient. Use only for explicit secret retrieval; the host prompts for approval because the value is sensitive.

Instructions

Reveal the raw signing secret of a webhook. SENSITIVE: by default the MCP masks secrets (returns secretSet:true/false). This tool returns the actual secret value and is marked destructive so the MCP host prompts for approval before it runs. Use only when the user explicitly needs the secret value.

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>",
      "uuid": "<uuid>"
    },
    "name": "gitflic_webhook_reveal_secret"
  }
}

Input Schema

Name	Required	Description
`raw`	No	Return the full, un-slimmed GitFlic response for THIS call (no token compression). Use when the default slim view dropped a field you need.
`uuid`	Yes
`project`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Nov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Adds real context beyond the annotations: the default masking behavior, the secretSet flag shape, and the fact that the MCP host will prompt for approval because the tool is destructive. Some of this restates destructiveHint, but the masking/prompt explanation is information the annotations cannot 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?

Three short sentences, front-loaded with the action and the sensitivity warning, with no redundant or filler wording.

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?

Covers the sensitive-data risk and what is returned, which is the main complexity here, but says nothing about required identifiers or auth requirements for a 3-parameter tool. With no output schema, more detail on the returned payload would help.

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?

With only 33% schema description coverage, the description carries the burden for the undocumented parameters, yet it never mentions 'project' or 'uuid' — the two required parameters. Only 'raw' is documented, and only in the schema itself.

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 ('Reveal the raw signing secret of a webhook') and immediately contrasts it with the default masked behavior, so an agent can distinguish it from the ordinary webhook-fetch sibling without inspecting schemas.

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 an explicit usage constraint ('Use only when the user explicitly needs the secret value') and explains that normal calls return secretSet:true/false instead. It stops short of naming a specific alternative tool, leaving the agent to infer that the default webhook-get is the fallback.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server