Skip to main content
Glama

Manage applications

manage_applications
Destructive

Add a job to the queue, pass on one, mark one not interested or a favourite, prepare one now, apply to the ready ones, choose its résumé, edit its packet or rate the queue. Actions: add_job, pass, not_interested, undo_not_interested, favorite, unfavorite, approve_all, prepare_now, choose_resume, edit_packet, rate_queue. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "manage_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
paramsNoFields for the action. Call with action "help" to list each action's fields.
application_idNoAn application's id from get_applications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "add_job",
      -  "pass",
      -  "choose_resume",
      -  "edit_packet",
      -  "rate_queue",
      -  "help"
      -]New value: +[
      +  "add_job",
      +  "pass",
      +  "not_interested",
      +  "undo_not_interested",
      +  "favorite",
      +  "unfavorite",
      +  "approve_all",
      +  "prepare_now",
      +  "choose_resume",
      +  "edit_packet",
      +  "rate_queue",
      +  "help"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "add_job",
      -  "pass",
      -  "choose_resume",
      -  "answer_questions",
      -  "edit_packet",
      -  "rate_queue",
      -  "help"
      -]New value: +[
      +  "add_job",
      +  "pass",
      +  "choose_resume",
      +  "edit_packet",
      +  "rate_queue",
      +  "help"
      +]
  3. Added

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the description's job is to add specifics beyond that; instead it adds almost nothing. It never warns that approve_all applies to all ready items at once or whether pass/not_interested are reversible, despite 'undo_not_interested' implying some actions are not. The 'help' action is the only genuinely useful behavioral pointer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence narrates a dozen operations and is then immediately restated in the 'Actions:' list, so roughly half the text is redundant. No grouping, ordering, or prioritization is given to what is the most important information (the action enum and the help escape hatch).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 12-action dispatcher with a nested open params object and no output schema, the description should describe at least the highest-risk actions (approve_all, prepare_now) and the params contract. It instead offloads nearly everything to a runtime 'help' call, leaving the agent unable to invoke the tool correctly in a single step.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the free-form 'params' nested object (additionalProperties: true) is the real documentation gap – the description only says to call action "help" for its fields, forcing an extra round trip instead of explaining any field meaning. It also never explains how application_id interacts with or overrides params.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this is a multi-action job-application queue manager by naming concrete operations (add_job, pass, prepare_now, approve_all, edit_packet), which goes well beyond the generic title 'Manage applications'. However, it never distinguishes itself from close siblings like apply_to_job or get_applications, so an agent cannot tell which tool owns 'apply to the ready ones' versus the dedicated apply tool.

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?

Usage is implied through the action list – 'prepare one now', 'apply to the ready ones', 'rate the queue' suggest when each action applies – but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as apply_to_job or get_applications. The only concrete routing instruction is 'Call with action "help"', which is a discovery mechanism rather than selection guidance.

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.