Skip to main content
Glama
Sign In

Argorant

by com.argorant
OverviewDiscussionsAdmin

Check a send to a connected tool

argorant_integration_push_status
Read-onlyIdempotent

Show how a send to a connected sending tool stands, waiting for its export, sending, done or failed, with how many people were sent, were already in that campaign or were not accepted there. Use it after argorant_push_to_integration; to see the connected tools use argorant_list_integrations. It is free. More in the docs at https://docs.argorant.com/docs/agents/tools#send-to-other-tools and https://docs.argorant.com/docs/guides/send-to-other-tools

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": {
      "push_id": "<push_id>"
    },
    "name": "argorant_integration_push_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
push_idYesThe push_id from argorant_push_to_integration

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by naming the lifecycle states and the breakdown of counts (sent, already in campaign, not accepted), which tells the agent what a poll actually reveals.

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

Conciseness4/5

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

Front-loaded with what the tool reports and followed by usage routing and doc links; nothing is wasted. The state list ('waiting for its export, sending, done or failed') is slightly run-on, but it stays readable and informative.

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?

With an output schema covering return values and rich annotations covering safety, the description only needs purpose, sequencing and cost — all present. Minor gap: it does not say whether polling is needed repeatedly or whether statuses are terminal, though the state list implies this.

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 single push_id parameter is already documented in the schema as coming from argorant_push_to_integration. The description reinforces that provenance with 'Use it after argorant_push_to_integration' but adds no format, lifetime or reuse semantics beyond it, so the schema does the heavy lifting.

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 and resource ('Show how a send to a connected sending tool stands') and enumerates the exact states it reports (waiting for export, sending, done, failed) plus the counters returned. This clearly distinguishes it from argorant_push_to_integration, which initiates the send.

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 explicit sequencing ('Use it after argorant_push_to_integration') and routes the agent elsewhere for a related need ('to see the connected tools use argorant_list_integrations'). It also adds a cost signal ('It is free'), so the agent knows no credits are consumed when polling.

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

All Argorant 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