Skip to main content
Glama

track_application

Log a submitted job application with company, role, status, notes, and URL to monitor progress and manage follow-ups.

Instructions

Track a job application you have submitted

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": {
      "company": "<company>",
      "role": "<role>"
    },
    "name": "track_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
roleYes
notesNo
statusNoapplied
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose that this likely creates a persistent record, whether duplicate applications are allowed, how status defaults or transitions work, or what permissions are required.

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

Conciseness3/5

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

The single sentence is concise and front-loaded, but its brevity reflects under-specification rather than efficient communication for a five-parameter mutation tool.

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

Completeness1/5

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

Given five parameters, a status enum, required company/role fields, no output schema, and no annotations, the description is far too thin. It omits the information an agent needs to invoke this tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description mentions none of the five parameters. It provides no meaning for required fields (company, role), optional fields (url, notes), or the status enum and its default.

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 identifies a resource ('job application') and an action ('track'), but 'track' is ambiguous: it could mean creating a record, monitoring an existing one, or updating status. With siblings like update_application and list_applications, it does not clearly distinguish this as the record-creation tool.

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

Usage Guidelines2/5

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

It implies usage after an application is submitted, but gives no explicit when-to-use guidance, no exclusions, and no direction to alternatives such as update_application or list_applications for related tasks.

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