Skip to main content
Glama

User Activity Read Tool

user-activity-read
Read-only

List CRM activities for a client. Requires user_id; supports filtering, sorting and pagination.

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, author_id, content, scheduled_at, completed_at, completed_by, assigned_to, created_at, updated_at, activities.id, activities.user_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, author, assignee, completedBy, audits.
limitNoResults per page. Default 20, max 100.
actionYesAction to perform.
filtersNoPurity filter object. Keys are field names, values are operator objects. Example: {"status":{"$eq":"active"}}. Available fields: id, user_id, author_id, content, scheduled_at, completed_at, completed_by, assigned_to, created_at, updated_at, activities.id, activities.user_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, author, assignee, completedBy, audits.
user_idYesUser id. Required for all actions.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds 'Requires user_id', which is also in the schema, and mentions pagination/filtering but not beyond schema. No contradiction, but minimal additional behavioral context.

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?

A single sentence with no filler, front-loading the core purpose. It is appropriately sized and every word earns its place.

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 annotations covering safety and a schema that documents parameters, the description is largely adequate. It omits return format, but no output schema exists, so the description could do slightly more. Still, the operation is simple and well-scoped.

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 all parameters are already documented. The description's mention of 'filtering, sorting and pagination' reiterates schema content without adding syntax or format details. Baseline 3 applies because the schema carries the load.

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 states a specific verb ('List') and resource ('CRM activities for a client'), making the tool's purpose clear. It does not explicitly differentiate from sibling read tools like client-read, but the resource is distinct enough. A perfect score would name an alternative.

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 notes 'Requires user_id' but does not provide guidance on when to use this tool versus alternatives. It does not mention exclusions, contexts, or when to prefer a sibling like user-activity-write. The mention of filtering/sorting/pagination is a capability, not usage guidance.

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