Skip to main content
Glama

Get deliverability

get_deliverability
Read-onlyIdempotent

Delivery rates by day, destination carrier, or sending number.

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

Input Schema

NameRequiredDescriptionDefault
end_dateNoYYYY-MM-DD
group_byNoWhat to group the rates by
start_dateNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / group_by / description
      Added value: +"What to group the rates by"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds no further behavioral context such as date defaults, timezone handling, pagination, rate limits, or aggregation semantics, so it provides little beyond the structured metadata.

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?

The description is a single front-loaded fragment with no wasted words. It is unusually terse but structurally efficient for a simple read tool, so it earns high conciseness despite being under-specified elsewhere.

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

Completeness3/5

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

Given the simple three-parameter schema and rich annotations, the description is minimally adequate for selecting the tool. However, with no output schema and no explanation of default date ranges or aggregation behavior, it leaves some operational details implicit.

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 start_date, end_date, and group_by are already documented. The description mirrors the group_by choices but adds no extra meaning such as date-range defaults, timezone assumptions, or whether rates are percentages.

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 metric (delivery rates) and the dimensions by which it can be broken down (day, destination carrier, sending number), which makes the tool's purpose clear. It lacks an explicit verb and does not directly distinguish itself from nearby usage/reporting siblings, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as get_usage or get_customer_usage, and no exclusions or prerequisites are stated. The agent is left to infer usage from the metric name alone.

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.