Skip to main content
Glama

get_application

Read-only

Read one application the signed-in mentee owns: status, action_required, whether they can withdraw, and the Pinax message thread. Requires Authorization: Bearer. application_hash comes from list_applications.

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>"
    },
    "name": "get_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds genuinely useful context beyond that: the Authorization: Bearer requirement and the per-mentee ownership constraint that scopes what can be read. It says nothing about behavior on an invalid or unowned hash, which is the main remaining behavioral gap for a single-record fetch.

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?

Three tight sentences: the resource and its contents first, the auth constraint second, the parameter provenance last. Every clause carries information and nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values do not need spelling out, and the auth and ownership requirements are stated. For a one-parameter read tool this is close to complete; only failure behavior for a bad or foreign hash is absent.

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% for the single parameter, so the description carries the burden here. It does state where application_hash originates (list_applications), which is real semantic value, but it says nothing about the hash format, case sensitivity, or what an unrecognized hash produces.

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 gives a specific verb and resource ('Read one application'), names the ownership scope ('the signed-in mentee owns'), and enumerates what the payload contains (status, action_required, withdrawability, Pinax message thread). Adding 'application_hash comes from list_applications' cleanly separates it from the sibling that returns many applications, so an agent can pick between them 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 Guidelines4/5

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

It establishes the retrieval workflow by telling the agent to obtain application_hash from list_applications, which implies this tool is the follow-up call for a single known application. It does not explicitly exclude anything or point at the action siblings (withdraw_application, pay_application, send_application_message) for users who actually want to act, so the exclusions are left implicit.

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