Skip to main content
Glama
Sign In
gapify-mcp-server

gapify-mcp-server

by mh-zeynal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Automation Rule: Remove a automation rule from account

gapify_remove_automation_rule
DestructiveIdempotent

Permanently delete an automation rule from a Gapify account by its ID when the rule is no longer needed.

Instructions

Remove an automation rule from the account [Automation Rule] DELETE /api/v1/accounts/{account_id}/automation_rules/{id} Auth: User API key (header api-access-token). Destructive: this permanently deletes the resource. Text values may be written in Persian (Farsi) or any other language and are sent unchanged; IDs, numbers and phone numbers may use Persian or Arabic-Indic digits.

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": {
      "account_id": "<account_id>",
      "id": "<id>"
    },
    "name": "gapify_remove_automation_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the automation rule to be deleted
account_idYesThe numeric ID of the account

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so 'Destructive: this permanently deletes the resource' largely repeats structured data. What the description genuinely adds is the authentication requirement (User API key via `api-access-token` header) and the note about Persian/Arabic-Indic digit handling. It says nothing about the response body or error behavior on a missing ID.

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

Conciseness3/5

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

Purpose, endpoint and auth are front-loaded and efficient. However, the closing sentence about text values being written in Persian is boilerplate for a tool with no free-text parameters, so it does not fully earn its place.

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

Completeness4/5

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

For a two-parameter delete with full schema coverage and annotations carrying the safety profile, the description supplies path, verb and auth, which is enough to invoke it correctly. No output schema exists, so the lack of return-value detail is acceptable.

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%, with both `id` and `account_id` documented, so the baseline is 3. The description adds only a marginal hint that IDs may use Persian/Arabic-Indic digits — useful but not substantial beyond the 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?

States a specific verb ('Remove') plus resource ('automation rule') scoped to the account, and pairs it with the concrete endpoint DELETE /api/v1/accounts/{account_id}/automation_rules/{id}. An agent can distinguish it from gapify_add_automation_rule, gapify_update_automation_rule and gapify_get_automation_rule purely from the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The action is unambiguous, but the description never says when to choose this over alternatives or what prerequisites exist (e.g., rule must exist, permissions beyond the API key). Usage is implied by the verb only, with no exclusions or routing guidance.

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