Skip to main content
Glama

AgentPMT - Marketplace For Autonomous Agents

AgentPMT Send Human Request

AgentPMT-Send-Human-Request

AgentPMT Send Human Request - Send a request or notification to the human who owns your budget, then check their decision. Every send is delivered to the human by email, by push notification in the AgentPMT mobile app, and as a notice in the Messages tab of the AgentPMT dashboard; they approve or deny from any of the three. Use action=send with request_type enable_tool or credential_setup (id = product ObjectId, required), enable_workflow (id = workflow ObjectId, required), add_funds, other, or notification_only, plus a plain-language request (max 5000 characters). Approving enable_tool or enable_workflow adds the target to the current budget automatically; approving add_funds completes a credit purchase; approving credential_setup stores the connection credentials. send returns mobile_request_id and approval_required. When approval_required is true, poll with action=check_response and request_id until status is approved, denied, or expired, then read decision_notes and action_result before continuing. notification_only never requires approval and must not be polled. Free, no credentials required, always available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoProduct/workflow ObjectId for access requests, or optional target identifier for check_response lookup
actionNoOperation to perform: send (default) or check_response. Only use check_response when send returned approval_required=true.send
requestNoFreeform request body to send to the user (required when action=send). Web URLs become clickable in email. Use [link label](https://example.com) for an inline link or [button: Button label](https://example.com) for a button.
request_idNoMobile approval request ObjectId to check when action=check_response.
request_typeNoRequest type: add_funds, enable_tool, enable_workflow, notification_only, other (required when action=send). Use notification_only to send a message that does not require approval; do not wait after sending.
include_requestNoWhen action=check_response, include the full request record in the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / request / description
      Previous value: -"Freeform request body to send to the user (required when action=send)"New value: +"Freeform request body to send to the user (required when action=send). Web URLs become clickable in email. Use [link label](https://example.com) for an inline link or [button: Button label](https://example.com) for a button."
  2. Changed3 schema fields changed
    • addedInput schema / properties / id / default
      Added value: +null
    • addedInput schema / properties / request / default
      Added value: +null
    • addedInput schema / properties / request_type / default
      Added value: +null
  3. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed2 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"Operation to perform: send (default) or check_response."New value: +"Operation to perform: send (default) or check_response. Only use check_response when send returned approval_required=true."
    • changedInput schema / properties / request_type / description
      Previous value: -"Request type: add_funds, enable_tool, enable_workflow, notification_only, other (required when action=send). Use notification_only to send a message that does not require approval."New value: +"Request type: add_funds, enable_tool, enable_workflow, notification_only, other (required when action=send). Use notification_only to send a message that does not require approval; do not wait after sending."
  5. 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 provided, the description carries the full behavioral burden and does so thoroughly. It discloses delivery channels, approval side effects for each request_type, return fields (mobile_request_id, approval_required), the polling loop with terminal statuses, and that notification_only never requires approval. It also states the tool is free and requires no credentials.

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 long but appropriate for a complex multi-action tool, and it is front-loaded with purpose before usage details. Every sentence adds operational value, covering delivery, actions, side effects, polling, and constraints without fluff.

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?

Given no annotations, no output schema, and six parameters, the description is complete enough for an agent to invoke the tool correctly. It explains the send/check_response loop, required inputs per request_type, side effects of approval, and the terminal statuses to read before continuing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful conditional semantics: id must be a product ObjectId for enable_tool/credential_setup, a workflow ObjectId for enable_workflow, and request is capped at 5000 characters with link/button formatting. It does not explain include_request, but that is well documented in the schema.

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?

The description states a specific verb ('send') and resource ('request or notification to the human who owns your budget'), plus the follow-up action. It clearly distinguishes this tool from siblings like Workflow-Creator or Tool-Search-and-Execution by focusing on human approval requests. An agent can tell what this tool does without opening the schema.

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

Usage Guidelines4/5

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

The description gives explicit when-to-use instructions for each action (send vs. check_response) and request_type, including that notification_only must not be polled. It does not name alternate sibling tools or when to prefer those, but for this tool's internal workflow the guidance is clear and actionable.

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