@vitrion/zentria-mcp

Official

Overview Schema Source Related Servers Discussions Admin

update-activity

Modify a sales activity's title, due date, assignee, or body, and set its status to done or cancelled with a reason. Keeps activity records accurate without recreating them.

Instructions

Update or complete/cancel a sales activity (PATCH /api/public/sales/activities/{id}). Set status to done or cancelled. Scope: sales:write.

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": "update-activity"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Activity id.
`body`	No
`dueAt`	No
`title`	No
`status`	No
`assigneeUserId`	No
`cancelledReason`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Sep 8, 2026

TDQS

B3.3/5.0

Behavior3/5

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

For a tool with no annotations, the description carries the full burden. It discloses the HTTP method (PATCH), the required auth scope (sales:write), and the key behavioral action of setting status. However, it does not mention side effects, whether updates are partial, reversibility, or response behavior, so transparency is only partial.

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?

The description is compact and front-loaded: the operation and endpoint come first, followed by the status-specific behavior and scope. Every sentence adds information and there is no filler.

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

Completeness2/5

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

With 7 parameters, no annotations, no output schema, and very low schema coverage, the description leaves too many gaps. It identifies the endpoint and statuses but does not cover the purpose of other fields, usage conditions, or expected behavior, making it incomplete for a tool this complex.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, and the description does not compensate. It adds meaning only for the status parameter by naming the done/cancelled values, but provides no semantics for body, dueAt, title, assigneeUserId, or cancelledReason. With coverage this low, the description should explain far more.

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 states a specific verb and resource: 'Update or complete/cancel a sales activity' and gives the exact PATCH endpoint. It also clarifies the key purpose of setting status to done or cancelled, making the tool's function unmistakable and distinct from other activity tools.

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?

The description offers no explicit guidance on when to use this tool versus alternatives like create-activity, get-activity, or list-activities. The endpoint and status operation imply usage context, but no when-to-use or when-not-to-use conditions are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server