Skip to main content
Glama

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. Only activities visible to the authenticated staff member are returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number. Default 1.
sortNoSort 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.
limitNoResults per page. Default 20, max 100.
actionYesAction to perform.
deal_idYesDeal id. Required for all actions.
filtersNoPurity 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.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the safe read-only profile, so the bar is lower. The description adds a non-obvious behavioral constraint: results are scoped to activities visible to the authenticated staff member, which is meaningful auth-driven filtering not captured in 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 tight sentences, front-loading purpose then the required parameter and capabilities. No filler or 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 read-list tool with full schema coverage, no output schema, and annotations carrying the safety profile, the definition covers purpose, required input, capabilities, and the visibility caveat. The return shape and total-count behavior are left unspecified but not critical.

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%, with pagination defaults, sort syntax, filter operators, and the action enum all documented in the schema itself. The description only restates that filtering/sorting/pagination exist and that deal_id is required, adding no syntax 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 distinguishes it from deal-activity-write and user-activity-read by the 'read' scope and 'deal' target. It does not name a sibling explicitly, but the resource is unmistakable.

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?

It gives a clear precondition ('Requires deal_id') and notes filtering/sorting/pagination support, which implies read-and-inspect use. However, it never states when to prefer this over user-activity-read or how it relates to deal-activity-write, leaving routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources