Skip to main content
Glama
Sign In

mailfloss

by com.mailfloss
OverviewDiscussionsAdmin

Get batch job results

get_batch_results
Read-onlyIdempotent

Per-email verdicts of a batch job, paginated (GET /v1/batch-verify/{id}/results). Pass next from the previous page to continue. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_batch_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob id.
nextNoOpaque cursor from the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this as a safe, read-only, idempotent operation. The description adds meaningful context beyond annotations: the endpoint path, pagination behavior, and the fact that it returns per-email verdicts.

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?

The description is extremely compact and front-loaded: it states the output, pagination model, endpoint, and key parameter usage in one sentence with no wasted text.

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 simple two-parameter read tool with full schema coverage and annotations, the description covers the key behavior: what is returned, pagination, and cost. A minor gap is that it does not state any prerequisite such as the batch job needing to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the parameters are already documented. The description adds operational meaning by explicitly telling the agent to pass `next` from the previous page to continue pagination, which is more than the schema alone provides.

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 clearly identifies the resource as per-email verdicts from a batch job and notes that results are paginated. It distinguishes this from a status check by focusing on verdicts, though it does not explicitly name get_batch_status as the 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?

It provides useful pagination guidance ('Pass `next` from the previous page to continue') and notes the operation is free. However, it does not say when to use this tool versus get_batch_status or whether the job must be completed first.

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

All mailfloss toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources