Skip to main content
Glama

Show a sender check and its report

get_sender_check
Read-only

Show one sender check, for free: status (checking, completed, failed, expired, pending_approval, cancelled) and, once completed, the report (kept 7 days, then score and counts only). Poll it by check_id while check_sender answers checking; list_sender_checks finds older ones. Unknown id: 404 sender_check_not_found.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "check_id": "sc_exampleexampleexample2"
    },
    "name": "get_sender_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_idYesCheck id (sc_...) from check_sender or list_sender_checks.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "check_id": "sc_exampleexampleexample2"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare this as a read-only, non-destructive, non-open-world getter, and the description adds real context beyond that: the check is free, the report is retained 7 days and then degrades to score and counts only, and an unknown id returns 404 sender_check_not_found. The retention/degradation detail and the error contract are exactly the behaviors an agent cannot get from annotations.

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?

One dense paragraph that front-loads the result (status/report), then alternatives, then the error case. Every clause carries distinct information — status enumeration, retention window, sibling routing, error code — with no filler.

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-only getter with no output schema, the description covers return shape, retention, polling workflow, sibling alternatives, and the not-found error. It does not describe the report's payload fields in any detail, but with no output schema declared that is a minor gap rather than a blocking one.

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 check_id (sc_... from check_sender or list_sender_checks) and passport_token are already fully documented in the schema. The description reinforces the polling use of check_id and adds the 404 outcome for an unknown id, but it does not add format or validation meaning beyond what is structured. Baseline 3 applies.

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?

"Show one sender check" is a specific verb+resource, and the description immediately enumerates what is returned: status values (checking, completed, failed, expired, pending_approval, cancelled) and, once completed, the report. It names the two siblings that could be confused with it (check_sender, list_sender_checks), so an agent can distinguish this from those tools 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?

It gives an explicit when-to-use rule: poll this tool by check_id while check_sender answers "checking", and use list_sender_checks for older checks. The alternative and the condition that selects it are both stated, leaving nothing 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.