Skip to main content
Glama
Sign In
Ploomes MCP Server

Ploomes MCP Server

by victorbenazzi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Finish Task

ploomes_tasks_finish
Idempotent

Complete tasks in Ploomes CRM by marking them as finished. This idempotent action safely updates task status.

Instructions

Mark a task as finished (completed) in Ploomes CRM. Sends {Finished: true} to the API. This is an idempotent action — finishing an already-finished task has no adverse effect.

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": "ploomes_tasks_finish"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTask ID to mark as finished

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide idempotency and non-destructive hints. The description adds the exact API payload ('Sends {Finished: true}'), but no further behavioral context (e.g., prerequisites, error cases). The description does not contradict annotations.

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 succinct sentences deliver essential purpose and idempotency information without redundancy.

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, single-parameter tool with strong annotations, the description is adequately complete. It covers what, how, and safety, though output or response format is omitted (no output schema needed).

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 description adds no new insight beyond the schema's parameter description. Baseline 3 applies.

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?

The description clearly states the specific action ('Mark a task as finished') and the resource ('Ploomes CRM tasks'). It distinguishes from siblings like ploomes_tasks_update by focusing solely on finishing.

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?

The description explicitly notes idempotency, advising safe repeated use. However, it does not mention when not to use it or alternatives (e.g., if updating other task fields would be preferable).

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