Skip to main content
Glama

AIsa Agent Mail

by one.aisa
OverviewDiscussionsAdmin

Inboxes - Query Metrics

get_agentmail_inbox_metrics
Read-onlyIdempotent

Query Metrics

Published reference price: $0.012 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
endNoEnd timestamp for the query.
limitNoLimit on number of buckets to return.
startNoStart timestamp for the query.
periodNoPeriod in number of seconds for the query.
inbox_idYesThe ID of the inbox.
descendingNoSort in descending order.
event_typesNoList of metric event types to query.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id",
-  "Authorization"
-]New value: +[
+  "inbox_id"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / Authorization
      Added value: +{
+  "description": "Bearer authentication",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id"
-]New value: +[
+  "inbox_id",
+  "Authorization"
+]
  3. Changed2 schema fields changed
    • removedInput schema / properties / Authorization
      Removed value: -{
-  "description": "Bearer authentication",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "inbox_id",
-  "Authorization"
-]New value: +[
+  "inbox_id"
+]
  4. First observed

TDQS

C2.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds only a per-request price note, which is useful cost context but does not explain metrics computation, event filtering, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely terse ('Query Metrics') and largely consumed by pricing boilerplate. For a 7-parameter inbox metrics endpoint, this is under-specification rather than appropriately concise, and nothing useful about the operation is front-loaded.

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

Completeness2/5

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

The tool has 7 parameters, many AgentMail siblings, and an output schema. The description does not state the inbox-specific scope or distinguish it from global metrics, leaving sibling selection and operational intent unclear despite rich structured fields.

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 all 7 parameters are already documented in the input schema. The description adds no parameter meaning, which is the expected baseline when the schema carries the full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only 'Query Metrics', which restates the title and tool name rather than specifying what metrics are queried, for which inbox, or how it differs from sibling tools like get_agentmail_metrics. It is a tautology rather than a clear verb+resource description.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_agentmail_metrics or get_agentmail_inbox_events. The agent receives no routing information.

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

All AIsa Agent Mail 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