Skip to main content
Glama
Sign In
handshake-mcp

handshake-mcp

by shahparam11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hs_get_applications

List your Handshake job applications with their current status. Filter by status (pending, accepted, declined, withdrawn, interview) and paginate results.

Instructions

List all your Handshake job applications with their current status.

Statuses: pending, accepted, declined, withdrawn, interview.

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": "hs_get_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (starts at 1).
per_pageNoResults per page.
statusNoFilter by status — omit to return all applications.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations provided. The description only mentions statuses and filtering, but does not disclose pagination behavior, rate limits, or whether it is read-only. Minimal disclosure beyond the obvious.

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?

Two sentences, front-loaded with the main purpose, then a clear list of statuses. No wasted words.

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?

Parameters are well-described, and an output schema exists. However, could mention pagination details (e.g., ordering) for full completeness.

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%, but the description adds specific enum values for status ('pending, accepted, declined, withdrawn, interview'), which goes beyond the schema's generic description. This adds meaningful context.

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 clearly states 'List all your Handshake job applications', using a specific verb and resource. It also lists possible statuses, distinguishing this tool from siblings like hs_apply (create) and hs_get_saved_jobs (different resource).

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

Usage Guidelines3/5

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

The description implies usage for viewing applications with optional status filtering, but no explicit guidance on when to use vs alternatives (e.g., hs_get_saved_jobs) or any exclusions.

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

Deploy Server

Other Tools