MisarReach MCP Server

get_sales_agent_actions

Read-onlyIdempotent

Review what your AI sales agent did today: actions taken, deals created, and replies sent. Use it to audit behavior and verify activity—read-only, today only.

Instructions

Get what the AI sales agent has done today, with summary stats — actions taken, deals created, replies sent.

This is the audit trail: use it to see what the agent did on the account's behalf, and to sanity-check its behaviour after enabling it. Covers TODAY only, so it is not the tool for historical reporting.

Reads only and changes nothing; it does not approve or undo any action. Requires an API key. No actions today is a normal answer, not an error.

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": "get_sales_agent_actions"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description still adds real value beyond them: today-only scope, the API-key requirement, the explicit statement that it does not approve or undo actions, and that an empty result is normal rather than an error. It omits return format/pagination detail, so not a full 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 paragraphs, each earning its place: purpose and contents first, scope/exclusion second, safety and edge-case semantics third. No filler or repetition of the title.

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 parameters, a rich annotation set, and a description that states scope, auth, edge-case semantics, return contents, and its non-destructive nature, an agent has everything needed to call this correctly. The absence of an output schema is not a gap because the description enumerates what comes back.

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?

The tool takes zero parameters, so per the baseline the schema carries the whole contract and there is nothing for the description to disambiguate. No parameter-related text is needed or missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get what the AI sales agent has done today') plus the return contents (actions taken, deals created, replies sent), and names its category ('This is the audit trail'). An agent can distinguish it from siblings like get_sales_agent_config or process_sales_agent without opening a schema.

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?

Gives explicit context ('sanity-check its behaviour after enabling it') and an explicit exclusion ('Covers TODAY only, so it is not the tool for historical reporting'). It does not name a specific alternative tool for historical reporting, so the routing is clear but not fully resolved to a sibling.

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