Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createPond

Create a pond in Follow Up Boss by specifying its name, the lead agent's user ID, and all member user IDs.

Instructions

Create a pond. name, userId (the pond lead agent) and userIds (all member user IDs) are all required.

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": {
      "name": "<name>",
      "userId": "<userId>",
      "userIds": "<userIds>"
    },
    "name": "createPond"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the pond.
userIdYesUser ID of the pond lead agent.
userIdsYesUser IDs of all pond members.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / properties / name / description
      Previous value: -"Pond name"New value: +"Name of the pond."
    • addedInput schema / properties / userId
      Added value: +{
      +  "description": "User ID of the pond lead agent.",
      +  "type": "integer"
      +}
    • addedInput schema / properties / userIds
      Added value: +{
      +  "description": "User IDs of all pond members.",
      +  "items": {
      +    "type": "integer"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "name"
      -]New value: +[
      +  "name",
      +  "userId",
      +  "userIds"
      +]
  2. First observedv1.1.1

TDQS

B3.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, openWorldHint=false, idempotentHint=false, and destructiveHint=false. The description adds no behavioral details beyond the create action, such as permissions, uniqueness/collision behavior, side effects, or what happens on failure.

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?

It is two short sentences, front-loads the action and resource, and contains no filler or redundant 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?

For a simple three-parameter create tool, it identifies the required inputs, but it omits useful context such as whether the lead must also appear in userIds, what a created pond returns, and how this relates to getPond/updatePond/listPonds.

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%, and the schema already describes name, userId, and userIds. The description repeats the roles (pond lead agent and all member user IDs) and requiredness but adds no format, constraints, or validation details beyond the schema.

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?

The description states a specific verb and resource: "Create a pond." This clearly distinguishes it from non-create siblings such as updatePond, getPond, and listPonds, though it does not explicitly name those alternatives.

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?

It gives no when-to-use guidance, no when-not-to-use conditions, and no comparison to updatePond or other pond-management tools. It only restates that the three parameters are required.

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