Skip to main content
Glama

SendGrid (Unofficial)

Sendgrid Get Stats

sendgrid_get_stats
Read-onlyIdempotent

Fetch email sending statistics (delivered, opens, clicks, bounces, etc.) for a date range. Example: get_stats({ start_date: "2024-01-01", end_date: "2024-01-31", _apiKey: "SG.xxx" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-sendgrid-api-key",
      "start_date": "2024-01-01"
    },
    "name": "sendgrid_get_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesSendGrid API key (SG.xxx)
end_dateNoOptional end date in YYYY-MM-DD format. Defaults to today.
start_dateYesStart date in YYYY-MM-DD format, e.g. "2024-01-01"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and repeatability profile is fully covered without the text. The description adds the metric list and confirms date-range scoping, but says nothing about aggregation granularity (per-day vs aggregate), rate limits, or authentication behavior beyond the inline key example.

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 the purpose and the enumerated metrics, followed by a compact usage example. The example largely duplicates the schema's own examples block, which is mild redundancy but not harmful.

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?

The tool is simple (3 params, flat), annotations fully cover safety semantics, the input schema documents every parameter at 100% coverage, and an output schema exists so return values need not be explained. Nothing an agent needs in order to invoke 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 coverage is 100%, with _apiKey, start_date, and end_date all already documented including the YYYY-MM-DD format and the 'defaults to today' behavior for end_date. The example call restates the same format information, so the description adds no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb (Fetch) and resource (email sending statistics) and enumerates the metrics returned (delivered, opens, clicks, bounces), scoped to a date range. It does not distinguish itself from sibling tools like get_bounces or get_blocks, which appear to be narrower slices of the same data, so an agent must infer the relationship.

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?

The date-range scoping and the inline example make the intended usage clear by implication, but there is no explicit statement of when to prefer this over the per-event siblings (get_bounces, get_blocks) or any exclusion conditions. Usage is inferred rather than declared.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.