Skip to main content
Glama
agentisend

agentisend

Get trust standing

get_trust_standing
Read-onlyIdempotent

Check the account's trust standing (ok, warning, throttled, or paused) and see the reasons, metrics, thresholds, and next review, especially after a send fails with trust_paused.

Instructions

Purpose: read the account's standing — ok, warning, throttled or paused — and the reasons behind it. Check it first when a send fails with trust_paused. NOT for: changing it. Standing follows delivery outcomes; nobody sets it directly. Returns: the state, each reason with its metric, value, threshold and window, and when it is next reviewed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
stateNook, warning, throttled or paused.
domainsNoStanding of each sending domain: state, streams, probation end and cap. The account line is state.
reasonsNoWhy the standing moved. Each reason carries metric, value and threshold. Empty while the state is ok.
streamsNoEach stream’s own standing: transactional and marketing.
probationNoTrue when the account itself is on probation.
probation_capNoMessages per 24 hours while on probation, or null.
next_review_atNoISO 8601 time, or null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description is not obliged to restate safety. It does add non-obvious behavior: the value is derived from delivery outcomes, cannot be set directly, and is periodically reviewed. The return shape is summarised but also covered by the output schema, so it stops just short of a 5.

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?

Four labelled clauses (Purpose / NOT for / trigger / Returns), each earning its place with zero filler. The most decision-relevant information, what the tool reads and when to call it, is front-loaded.

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 no-argument read tool with full annotations and an output schema, the definition covers purpose, trigger, exclusions and the essence of the response. Only the semantics of the thresholds themselves (how warning differs from throttled in practice) are left implicit.

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?

There are zero input parameters and 100% schema coverage, so there is nothing for the description to compensate for. It correctly spends no words on arguments and instead frames the call as parameterless 'check it first'.

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 read verb plus the exact resource ('the account's standing') and enumerates the possible states (ok, warning, throttled, paused). It also explicitly separates itself from mutation of the same concept, so an agent can place it immediately.

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?

Gives a concrete trigger to reach for it ('Check it first when a send fails with trust_paused') and an explicit exclusion ('NOT for: changing it'). The exclusion is reinforced with the causal explanation that standing follows delivery outcomes, leaving no ambiguity about who owns the value.

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