Skip to main content
Glama

get_verification

Fetch a verification job and its results by job_uuid, without billing anything. Use it to poll a verify_email call that returned still processing, or to re-read an earlier result; to submit an address use verify_email, and for a batch use get_batch_results. Returns the job status and, once it is completed, the verdict, score, and checks. Requires the results:read scope.

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": {
      "uuid": "<uuid>"
    },
    "name": "get_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesPublic job UUID returned by verify_email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / api_key
      Removed value: -{
      -  "description": "Optional. A pm_live_/pm_test_ key that owns the job; this call is read-only and bills no tokens, the key only selects whose job to fetch. Omit to fetch with your own session instead (needs the results:read scope).",
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does well: it discloses the billing trait ('without billing anything'), the required scope ('results:read'), and the return shape (status, then verdict/score/checks once completed). These are exactly the behaviors an agent needs for a read tool.

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?

Front-loads the core operation and its non-billing trait, then handles alternatives and returns in tightly packed sentences. Every sentence earns its place with no redundancy.

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?

For a single-param read tool with no output schema, the description covers the missing pieces: usage context, billing behavior, auth scope, and the shape of the return value. Nothing an agent needs 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% and the schema documents uuid as the public job UUID from verify_email. The description only restates 'by job_uuid', so it adds little beyond the schema; baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb (fetch), resource (verification job and its results), and scope (by job_uuid), then actively distinguishes itself from verify_email and get_batch_results. An agent can select it without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names when to use it (poll a still-processing verify_email call, re-read an earlier result) and routes to the alternatives for the other intents (submit via verify_email, batch via get_batch_results). Nothing is left to inference.

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