Skip to main content
Glama

send_application_message

Send a message on an open application's Pinax thread. Requires Authorization: Bearer. Use this before mentorship starts. After an active mentorship exists, use send_message instead. Do not include scheduling links.

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": {
      "application_hash": "<application_hash>",
      "content": "<content>"
    },
    "name": "send_application_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
application_hashYes

Output Schema

NameRequiredDescriptionDefault
hashNoPass to pay_application.
errorNo
statusNodraft, new, pending, accepted, rejected, withdrawn.
unreadNoTrue when the mentee has an unread Pinax message.
messageNo
pay_urlNoREST URL that accepts an MPP credential if credits are short.
payableNoTrue when the mentor accepted and payment is due.
messagesNo
next_stepNo
plan_hashNo
price_usdNo
created_atNo
credits_usdNo
mentor_nameNo
status_noteNo
can_withdrawNoTrue when withdraw_application will succeed.
dashboard_urlNo
action_requiredNoreply_to_mentor, waiting_on_mentor, book_intro_call, or start_mentorship.
mentor_usernameNo
sent_message_idNo
intro_call_scheduledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the write, open-world, non-destructive profile; the description adds the auth requirement (Bearer token) and the implicit precondition that the application must be open. It does not discuss delivery timing or throttling, but the presence of an output schema removes the need to describe returns.

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?

Five short, front-loaded sentences: purpose first, then auth, then lifecycle routing, then the content prohibition. Every sentence carries operative information 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 write tool with an output schema and existing annotations, the description covers routing, auth, and a key content restriction. The main residual gap is disambiguating the application_hash parameter explicitly rather than by implication.

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 0%, so the description must carry meaning for both parameters; it does so partially by implying application_hash targets an *open* application and by constraining message content (no scheduling links). It never explicitly maps these constraints to the named parameters or specifies hash format, leaving a gap.

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 (send), resource (message), and scope (an open application's Pinax thread), which distinguishes it from the general send_message sibling. An agent can pick the right tool without opening either 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?

Gives an explicit lifecycle condition ('Use this before mentorship starts') plus the named alternative for the other state ('After an active mentorship exists, use send_message instead'). It also adds a negative constraint ('Do not include scheduling links'), leaving little 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