> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools/platform-get-summary.md).

# platform\_get\_summary — Read platform activity

**Declared contract — reviewed 21 October 2026.** This page describes the tool exposed by the Autom Mate New connection in the inspected 71-tool profile. It does not establish support on every build or prove runtime success. Check the active connection and [installed product version](https://docs.autommate.com/userguide/start-here/documentation-scope-and-product-versions.md). Historical examples retain their original observation dates. Logical tool names may have a client-specific namespace prefix.

Read an operational summary for the connected tenant over `24h`, `7d` or `30d`. Choose the window explicitly when comparing activity.

## Declared request signature

The following is the exposed 21 October declaration; request types do not define an exhaustive response schema.

```ts
declare const tools: { mcp__codex_apps__autom_mate_new_platform_get_summary(args: { window?: "24h" | "7d" | "30d"; }): Promise<CallToolResult>; };
```

## Parameters

| Parameter | Type                  | Required | Meaning                                                            |
| --------- | --------------------- | -------- | ------------------------------------------------------------------ |
| `window`  | `24h`, `7d`, or `30d` | No       | Reporting window. The exposed schema does not specify the default. |

## Minimal request

The window is explicit because the exposed schema does not publish a default.

```json
{
  "window": "24h"
}
```

## Read the result

* Keep the selected window, observation time and returned scope with your summary. An aggregate does not establish the outcome of an individual request.
* Use run history and the specific execution record for current status or failure investigation. A 24-hour summary is not a replacement for a search filtered to `in_progress`.
* Read the fields actually returned. Missing or unavailable data must not be presented as zero, and activity counts must not be described as verified business outcomes.

## Permissions and retries

Read-only tenant summary. If access or collection fails, report that limitation instead of an empty operational period. Repeating a summary read does not start, stop or repair executions.

## Present a requested result

When the user asked to see this result, pass the returned `result_ref` to `show_result` once for the final requested answer. Do not show cards for intermediate lookups. A result reference expires after 15 minutes; read again if it has expired. This presentation step neither executes nor verifies a business action.

## Continue

* Next tools: [`runs_search`](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools/runs-search) · [`agents_get_health`](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools/agents-get-health).
* Workflow: [Inspection tool contracts](https://docs.autommate.com/userguide/mcp-and-ai-reference/inspection-tool-contracts.md).
* Worked reference: [Read platform summaries schedules and agent health](https://docs.autommate.com/userguide/mcp-and-ai-reference/read-platform-summaries-schedules-and-agent-health.md).
* [MCP tool reference](https://docs.autommate.com/userguide/mcp-and-ai-reference/tools).
