datapulse-my

Overview Schema Source Related Servers Score Discussions Admin

Summarize Aggregate Tool Usage

usage_summary

Read-onlyIdempotent

Get anonymous tool usage totals and breakdowns for any inclusive ISO date range. Retrieve call counts, outcomes, tool and dataset usage, and trust distribution.

Instructions

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_distribution (per-status counts of cited datasets) for the inclusive range. Legacy identity fields are ignored.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`since`	Yes	Inclusive ISO start date YYYY-MM-DD, e.g. '2026-08-01'.
`until`	Yes	Inclusive ISO end date YYYY-MM-DD, e.g. '2026-08-07'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.12.0Sep 9, 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"
+]

Addedv1.0.2Sep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, and the description adds useful behavioral context beyond those: results are anonymous, the date range is inclusive, and legacy identity fields are ignored. It also names the output fields, which orients the caller even though an output schema exists. No contradiction with 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?

Three compact sentences convey the action, date scope, returned fields, and an important caveat. The key verb phrase is front-loaded, and every sentence earns its place without repeating annotations or schema 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?

For a simple 2-parameter, read-only aggregate tool, the description is complete: parameters are fully documented, annotations cover safety behavior, an output schema exists, and the anonymous/legacy-identity caveat adds context not available elsewhere. An agent has everything needed to invoke and interpret this tool correctly.

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 fully documents the two ISO date parameters with examples. The description reinforces that the range is inclusive but does not add meaningful parameter semantics beyond what the schema provides, so the high-coverage baseline of 3 applies.

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?

The description uses a specific verb-resource pairing: 'Aggregate anonymous tool usage' over an explicit inclusive ISO date range. It clearly distinguishes this aggregate analytics tool from the data-retrieval and verification siblings, and lists the returned aggregate fields so an agent understands exactly what the tool produces.

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?

The description establishes clear context: this is the tool for aggregate, anonymous usage summaries over a date range. The phrases 'anonymous' and 'Legacy identity fields are ignored' impliedly warn against using it for per-identity or per-user analysis, though it does not explicitly name sibling alternatives or state when-not-to-use conditions.

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