Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

removeTagFromPerson

DestructiveIdempotent

Removes one tag from a person while leaving other tags untouched (case-insensitive), avoiding replacement of all tags.

Instructions

Remove one tag from a person, leaving other tags untouched (case-insensitive). Use this instead of updatePerson tags, which replaces ALL tags.

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": {
      "id": "<id>",
      "tag": "<tag>"
    },
    "name": "removeTagFromPerson"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPerson ID.
tagYesTag to remove (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / id / description
      Previous value: -"Person ID"New value: +"Person ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / tag / description
      Previous value: -"Tag to remove (case-insensitive match)"New value: +"Tag to remove (case-insensitive)."
  2. First observedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to scope that destruction — and it does: exactly one tag is removed and other tags survive, which is the key safety distinction versus a full tag replacement. It does not say what happens if the tag is absent or what permissions are required, leaving modest gaps.

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?

Two sentences, zero filler. The behavioral guarantee is front-loaded and the disambiguation against updatePerson follows immediately.

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 simple two-parameter mutation with annotations covering the safety profile and no output schema, this is nearly complete. The only real omission is the outcome when the tag is not present on the person, which matters for an idempotent operation.

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 tag documented, so the baseline is 3. The description's case-insensitive note for the tag largely restates the schema's own parenthetical rather than adding new semantics.

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 (remove one tag from a person) along with the exact scope: only the named tag, all others untouched. It then names the sibling it is not (updatePerson tags), so an agent can distinguish the two 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?

Explicitly routes the agent: use this instead of the tags field on updatePerson, which replaces ALL tags. That is a real decision rule against a sibling. It doesn't cover edge cases (multiple tags to remove, tag not present on the person), so it falls short of a full when/when-not treatment.

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