Wayfront

Deal Activity Read Tool

deal-activity-read

Read-only

List logged and scheduled activities for a deal. Requires deal_id; supports filtering, sorting and pagination. Content is returned as stored HTML.

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": {
      "action": "<action>",
      "deal_id": "<deal_id>"
    },
    "name": "deal-activity-read"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number. Default 1.
`sort`	No	Sort fields. Append :asc or :desc for direction (default :asc). Example: ["created_at:desc"]. Available fields: id, user_id, deal_id, author_id, content, scheduled_at, completed_at, completed_by, assigned_to, created_at, updated_at, activities.id, activities.user_id, activities.deal_id, activities.author_id, activities.content, activities.scheduled_at, activities.completed_at, activities.completed_by, activities.assigned_to, activities.created_at, activities.updated_at, user, deal, author, assignee, completedBy, audits.
`limit`	No	Results per page. Default 20, max 100.
`action`	Yes	Action to perform.
`deal_id`	Yes	Deal id. Required for all actions.
`filters`	No	Purity filter object. Keys are field names, values are operator objects. Example: {"status":{"$eq":"active"}}. Available fields: id, user_id, deal_id, author_id, content, scheduled_at, completed_at, completed_by, assigned_to, created_at, updated_at, activities.id, activities.user_id, activities.deal_id, activities.author_id, activities.content, activities.scheduled_at, activities.completed_at, activities.completed_by, activities.assigned_to, activities.created_at, activities.updated_at, user, deal, author, assignee, completedBy, audits.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: content comes back as stored HTML, which affects how an agent should handle the output, plus confirmation of filter/sort/pagination support. It stops short of describing return shape or default ordering, which keeps it from a 5.

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?

Three short sentences, front-loaded with the resource and scope, then the required parameter, then the output caveat. No redundant or filler wording; each sentence carries distinct information.

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 read-only list tool with fully documented schema and clear annotations, the definition covers purpose, the required key and the HTML output caveat. Minor gaps remain: whether both completed and scheduled activities are returned together, default sort order, and the response envelope, but none block correct invocation.

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 description coverage is 100%, so every parameter including the sort fields list and filter object is already documented. The description only restates that deal_id is required and that filtering/sorting/pagination exist, adding no operator or format detail beyond the schema; baseline 3 applies.

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 (List) and resource (logged and scheduled activities for a deal), which is enough to distinguish it from deal-activity-write and from user-activity-read. It doesn't explicitly name a sibling, but the 'for a deal' scoping does the disambiguation work.

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 description gives a prerequisite ('Requires deal_id') and notes that filtering, sorting and pagination are supported, which implies usage context. It never says when to prefer this over deal-activity-write or user-activity-read, and gives no exclusions, so guidance is implied rather than stated.

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

All Wayfront tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?