DataPulse

Summarize Aggregate Tool Usage

usage_summary

Read-onlyIdempotent

Aggregate anonymous tool usage for an inclusive ISO date range, e.g. 2026-08-01 to 2026-08-07. Returns total_calls, by_outcome, by_tool, by_dataset, trust_verdict_calls (the count of trust_verdict records regardless of outcome or result shape), and trust_distribution (counts of returned trust verdicts by published score band: 90-100, 75-89, 50-74, 25-49, 0-24) for the inclusive range. Use it for aggregate tool activity; do not use it to find data-quality risks—use find_stale, find_anomalies, find_deteriorating, find_recovering, find_unreliable, or find_schema_drift instead. It reads persisted usage records, so zero totals mean no retained records in that range; DataPulse is read-only, requires no API key, and the edge limits clients to roughly one request per second with a small burst, so pace or retry.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	Yes	Inclusive first day of the persisted-record window, e.g. '2026-08-01'; it must not be after until.
`until`	Yes	Inclusive last day of the persisted-record window, e.g. '2026-08-07'; it must not be before since.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 21, 2026

changedInput schema / properties / since / description

Previous value: -"Inclusive ISO start date YYYY-MM-DD, e.g. '2026-08-01'."New value: +"Inclusive first day of the persisted-record window, e.g. '2026-08-01'; it must not be after until."

changedInput schema / properties / until / description

Previous value: -"Inclusive ISO end date YYYY-MM-DD, e.g. '2026-08-07'."New value: +"Inclusive last day of the persisted-record window, e.g. '2026-08-07'; it must not be before since."

Changed2 schema fields changedSep 6, 2026

removedInput schema / properties / buyer_id

Removed value: -{
-  "description": "Buyer identifier, e.g. 'pro-default' or 'anonymous'.",
-  "examples": [
-    "pro-default"
-  ],
-  "minLength": 1,
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "buyer_id",
-  "since",
-  "until"
-]New value: +[
+  "since",
+  "until"
+]

AddedAug 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description adds non-redundant behavioral context: it reads persisted records, zero totals mean no retained records, requires no API key, and the edge is rate-limited to roughly one request per second. This goes beyond the structured 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?

Every sentence earns its place: purpose, return shape, when-to-use/alternatives, and behavioral caveats. The most important scoping and exclusion information is front-loaded before lower-level details.

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?

Complete for a read-only aggregate tool: parameters are fully covered, return values are explained, alternatives are named, and operational constraints (rate limit, no API key, zero-total meaning) are given. Nothing needed to call it correctly is missing.

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 the schema already documents both parameters with examples and constraints. The description adds the aggregate 'inclusive ISO date range' framing and an example range, but does not carry the semantic burden.

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 ('aggregate') and resource ('tool usage') with an explicit inclusive ISO date range and enumerates the exact return metrics. It also distinguishes itself from the data-quality find_* siblings, so an agent can select it correctly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use it for 'aggregate tool activity' and clearly says not to use it for data-quality risks, naming six alternatives in the same tool family. This is unambiguous routing guidance with no reliance on inference.

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

All DataPulse tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.