Skip to main content
Glama

get_inbox_response_metrics

Read-onlyIdempotent

Read aggregate Inbox response metrics for the approved business over the last 7 or 30 days. Median first response is in milliseconds.

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

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the useful detail that median first response is returned in milliseconds and that the window is limited to 7 or 30 days, but says nothing about what other aggregate metrics are included or how empty data is handled.

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?

Two short sentences, front-loaded with the core action and scope, with the unit detail appended where it belongs. No filler.

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?

For a single-parameter read tool with an obvious schema and strong annotations, most of what an agent needs is present. However, it advertises 'aggregate ... metrics' (plural) while explaining only the median first response, so a caller cannot anticipate the full return shape without an output schema.

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 0%, so the description carries the burden for the single 'days' parameter; it states the two allowed windows (7 or 30) and that they are trailing periods, which the raw schema's const values do not express. It omits the default of 30, leaving that to 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?

Specific verb and resource ('Read aggregate Inbox response metrics') with scope ('for the approved business over the last 7 or 30 days'). It is easy to distinguish from the sibling tools, none of which report metrics, though the description does not name any alternative.

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 the verb 'Read' and the time-window framing, so an agent can infer this is for fetching summary response statistics. There is no explicit when-to-use or when-not-to-use guidance, and no mention of how it relates to per-conversation tools like summarize_inbox_conversation.

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.

Resources