Skip to main content
Glama
Sign In

Emailchaser

by com.emailchaser
OverviewDiscussionsAdmin

Get inbox placement stats by date

get_inbox_placement_stats_by_date
Read-only

Rolls completed inbox placement runs up by UTC calendar day over a window, for a trend. Defaults to the last 30 days. Days on which nothing ran are ABSENT from the series rather than zero: never report a missing day as 0% placement, it means nobody ran a test that day.

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_inbox_placement_stats_by_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the window, RFC3339. Defaults to now
fromNoStart of the window, RFC3339, e.g. 2026-08-01T00:00:00Z. Defaults to 30 days ago

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description could have coasted. Instead it discloses a non-obvious output semantic: days with no runs are omitted rather than zeroed, with an explicit warning not to report them as 0% placement — exactly the kind of interpretive trap that causes wrong conclusions.

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?

Two sentences, front-loaded with what the tool produces before the caveat. Slight redundancy in repeating the 30-day default already present in the schema prevents a perfect score, but nothing else is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, two-parameter aggregation with full schema coverage and no output schema, this covers what an agent needs to call it correctly and to interpret gaps. It does not describe which placement metrics appear per day beyond the day key, but the annotations and schema carry the rest.

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 coverage is 100%, and the schema already documents 'from' and 'to' with their defaults and RFC3339 format. The description's contribution is the UTC bucketing granularity and a restatement of the 30-day default; it adds no format or boundary details beyond the schema.

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 verb and resource: rolls up completed inbox placement runs by UTC calendar day over a window. The aggregation framing distinguishes it from single-run siblings like get_inbox_placement_run, though no sibling is named explicitly.

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 implied by 'for a trend' plus the default 30-day window, which tells the agent this is the time-series view rather than the per-run view. There is no explicit when-not-to-use or named alternative, so the agent must infer the boundary itself.

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

All Emailchaser toolsInspect
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.

Resources