Skip to main content
Glama

Outil.io

List activities

list_activities
Read-only

Journal des activités (appels, rendez-vous, notes, courriers) d’un prospect, d’un contact ou d’une opportunité, les plus récentes d’abord.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
sinceNo
untilNo
dealIdNo
contactIdNo
prospectIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/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 the safety profile is covered. The description adds genuine behavioral context beyond that by stating results are returned most-recent-first, but it says nothing about pagination, default limit behaviour, or how the three entity scopes interact when several are supplied.

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?

A single compact sentence with the resource front-loaded, followed by the scoping entities and the ordering. Nothing is redundant, though the length is low partly because the description is under-specified rather than because it is disciplined.

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, zero required, and no output schema, an agent needs to know defaults for limit, the accepted format for since/until, and what happens with no entity filter — none of which is stated. The description is adequate for identifying the tool but insufficient to invoke it correctly without inspecting the raw schema.

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 0% across 7 parameters, so the description must carry the meaning and largely does not. It gestures at the entity scoping (prospect/contact/deal, which map loosely to prospectId/contactId/dealId) and lists some activity types, but omits the limit, since and until parameters entirely and lists only four of the eight enum values (email, sms, visit and other are missing).

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 names a specific resource — an activity log (calls, meetings, notes, letters) — and the entities it can be scoped to (prospect, contact, deal), plus the ordering (most recent first). This is clearly an activity-listing tool, distinguishable from siblings like list_prospect_follow_ups or list_conversations, though the implicit 'list' verb is only conveyed by the name.

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?

Usage is only implied: you read it as 'use this to see the activities of a given prospect/contact/deal'. There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., the follow-up list tool) that would tell an agent when to pick one over the other.

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.