Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

updatePond

DestructiveIdempotent

Modify a pond by ID, including its name or member user IDs. When replacing membership, provide the complete user ID list because it overwrites existing members.

Instructions

Update a pond by ID. If userIds is sent, send the COMPLETE member list; it replaces the existing one.

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

Input Schema

NameRequiredDescriptionDefault
idYesPond ID.
nameNoName of the pond.
userIdsNoComplete list of member user IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • changedInput schema / properties / id / description
      Previous value: -"Pond ID"New value: +"Pond ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / name / description
      Previous value: -"Name"New value: +"Name of the pond."
    • addedInput schema / properties / userIds
      Added value: +{
      +  "description": "Complete list of member user IDs.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "name"
      -]New value: +[
      +  "id"
      +]
  2. First observedv1.1.1

TDQS

A3.7/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, but the description adds the concrete consequence an agent needs: userIds acts as a full replacement of the existing member list. That explains the source of the destructive behavior rather than just restating it. It does not cover partial-update semantics for omitted fields like name.

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?

Two short sentences, operation first and the risky parameter caveat second, with no filler. Capitalizing COMPLETE is slightly noisy but effectively emphasizes the most failure-prone detail.

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?

A simple three-parameter mutation tool whose safety profile is carried by annotations and whose parameters are fully schema-documented; the description covers the one non-obvious semantic. Adding a note on whether omitted fields are left unchanged would close the remaining gap.

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 coverage is 100%, so all three parameters are already documented, which sets the baseline at 3. The description adds one meaningful clarification, that userIds is a replacement rather than an append, but says nothing about how an omitted name is treated.

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 a specific verb and resource with its identifier: 'Update a pond by ID.' That cleanly separates it from getPond, createPond, and listPonds in the sibling set. It stops short of naming alternatives explicitly, but the operation 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 Guidelines3/5

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

The second sentence gives a real usage rule for one parameter (when sending userIds, send the complete list), which is genuine when/how guidance. However, there is no statement of when to prefer this tool over siblings or any prerequisite/exclusion, so guidance is partial rather than complete.

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