Skip to main content
Glama
vinayvobbili

jobwatch

by vinayvobbili
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_application_package

Destructive

Store the exact files, form answers, and note submitted with a job application so you can retrieve them later. Call after submission to keep a copy of what was actually sent.

Instructions

Keep what was sent with an application, as copies: files (local paths to the resume PDF, cover letter... exactly as uploaded), answers (the form's questions and the answers given, [{question, answer}]; replaces any saved before) and note (a cover letter or message pasted into the form). Call it once the person has submitted, with what they actually sent; get_application_package reads it back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesThe job: its key as other tools return it (source:board:posting id, e.g. greenhouse:acme:4012345), just the posting id, or the company's name when that names one job (the one queued or applied to there). When it matches several, the error lists their keys.
noteNoA cover letter or message pasted into the form.
filesNoLocal paths to the files exactly as uploaded (resume PDF, cover letter...). Copies are kept.
answersNoThe form's questions and the answers given, as [{"question": ..., "answer": ...}]. Replaces any saved before.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.3
    • addedInput schema / properties / answers / description
      Added value: +"The form's questions and the answers given, as [{\"question\": ..., \"answer\": ...}]. Replaces any saved before."
    • addedInput schema / properties / files / description
      Added value: +"Local paths to the files exactly as uploaded (resume PDF, cover letter...). Copies are kept."
    • addedInput schema / properties / key / description
      Added value: +"The job: its key as other tools return it (source:board:posting id, e.g. greenhouse:acme:4012345), just the posting id, or the company's name when that names one job (the one queued or applied to there). When it matches several, the error lists their keys."
    • addedInput schema / properties / note / description
      Added value: +"A cover letter or message pasted into the form."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false. The description adds useful context beyond them: files are kept 'as copies' (not moved), and answers 'replace any saved before', clarifying partial-overwrite semantics. It does not cover auth or error behavior, but the added nuance is real.

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?

It is a single dense sentence with parenthetical glosses for each parameter, front-loading the purpose before the usage instruction. The nested parentheses make it slightly awkward, but every clause carries information.

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 destructive save tool with no output schema, the description covers what is stored, when to call it, and how to read it back. It omits what the call returns (e.g. a confirmation or the saved key), which would round it out, but nothing critical is missing.

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 100%, so the schema already documents all four parameters well. The description largely restates the same parameter meanings ('exactly as uploaded', 'replaces any saved before'), adding little beyond what the schema already provides.

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 and resource: keeping copies of what was sent with an application (files, answers, note). It explicitly contrasts with the read counterpart, get_application_package, so an agent can distinguish it from its closest sibling 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 gives a clear timing condition ('Call it once the person has submitted, with what they actually sent') and names the read alternative ('get_application_package reads it back'). It does not spell out when not to call it (e.g. before submission is complete), but the context is strong.

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