Skip to main content
Glama

Wayfront

by com.wayfront.mcp
OverviewDiscussionsAdmin

Deal Activity Write Tool

deal-activity-write
Destructive

Create, update, delete or complete deal activities. Requires deal_id; update/delete/complete also require activity_id belonging to this deal and visible to you. Create and update require content. Create accepts scheduled_at and assigned_to for a follow-up; update can reschedule/reassign pending activities and preserves omitted scheduling fields. Delete permanently removes the activity from the deal and contact. Activities also appear on the contact and changes use the normal permissions and history logs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform.
contentNoActivity content/notes (plain text, max 10000 chars). Required for "create" and "update".
deal_idYesDeal id. Required for all actions.
activity_idNoActivity ID. Required for "update", "delete" and "complete".
assigned_toNoOptional staff assignee for scheduled activities. On update, omit to preserve or pass null to unassign.
scheduled_atNoOptional future date/time (ISO 8601). Create without it logs a completed activity. Update only accepts it for a pending activity; omit to preserve the due date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "create",
-  "complete"
-]New value: +[
+  "create",
+  "update",
+  "delete",
+  "complete"
+]
    • changedInput schema / properties / activity_id / description
      Previous value: -"Activity ID. Required for \"complete\"."New value: +"Activity ID. Required for \"update\", \"delete\" and \"complete\"."
    • changedInput schema / properties / assigned_to / description
      Previous value: -"Optional staff user ID to assign. Only used when scheduled_at is provided."New value: +"Optional staff assignee for scheduled activities. On update, omit to preserve or pass null to unassign."
    • changedInput schema / properties / assigned_to / type
      Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
    • changedInput schema / properties / content / description
      Previous value: -"Activity content/notes (plain text, max 10000 chars). Required for \"create\" action."New value: +"Activity content/notes (plain text, max 10000 chars). Required for \"create\" and \"update\"."
    • changedInput schema / properties / scheduled_at / description
      Previous value: -"Optional future scheduled date/time for \"create\" (ISO 8601). If omitted, the activity is logged as completed."New value: +"Optional future date/time (ISO 8601). Create without it logs a completed activity. Update only accepts it for a pending activity; omit to preserve the due date."
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses that delete permanently removes the activity from both the deal and contact, that update preserves omitted scheduling fields, and that changes flow through normal permissions and history logs. This is meaningful mutation and side-effect context an agent needs before acting.

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?

Five dense sentences, all front-loaded around the action requirements and then the behavior notes; each sentence carries distinct information with no filler. It is slightly long but nothing reads as redundant.

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

Completeness5/5

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

With no output schema needed and annotations covering the safety profile, the description still covers all four actions, their parameter requirements, scheduling behavior, and delete side effects, leaving nothing an agent needs to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so per-field meaning is already documented; the description still adds cross-action semantics, e.g. that update only accepts scheduled_at for a pending activity and can reschedule/reassign, and that a create without scheduled_at logs a completed activity. This goes slightly beyond the per-parameter schema text.

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 opens with a specific set of verbs (create, update, delete, complete) acting on a clear resource (deal activities), so the tool's function is unambiguous. It does not explicitly distinguish itself from the deal-activity-read sibling, relying on the write/read naming convention instead, which keeps it from a full 5.

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?

It gives clear conditional guidance tied to actions: deal_id always required, activity_id required for update/delete/complete, content required for create/update, and scheduling fields only apply on create/update. It stops short of naming alternatives or stating when not to use this tool versus the read counterpart.

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

All Wayfront toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources