Skip to main content
Glama

jobctl

by io.github.DmytroRybka

Attach company analysis

attach_analysis
Destructive

Attach a markdown company analysis (research you produced) to an application. Single document per application — a new call REPLACES the previous one. Max 100000 bytes (~100 KB) of utf-8. The user reads it in the dashboard, e.g. before an interview. Example: attach_analysis({application_id: "…", markdown: "# Bosch\n\n## Culture…"}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownYesThe analysis as markdown
application_idYes

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true), description adds key details: replacement on new call, max size 100KB, and markdown format. No contradictions.

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 plus example, every sentence adds value. Front-loaded with purpose. No redundancy.

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

Completeness5/5

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

For a tool with 2 params and no output schema, description covers all: purpose, behavior, size limit, example. Leaves no ambiguity for correct invocation.

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?

With only 50% schema coverage, description compensates by explaining markdown purpose and size limit, and includes example showing both parameters. Application_id is only described via schema, but UUID format is clear.

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?

Description clearly states the tool attaches a markdown company analysis to an application, and distinguishes from siblings like add_note or attach_file by specifying it's for research and single document replacement.

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?

Description explains when to use (attach analysis for dashboard reading before interview) and implicitly when not (due to replacement behavior), but does not explicitly contrast with sibling tools.

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

All jobctl toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: application, note, analysis attachment, file attachment, interview file, application detail, due actions, planned schedule, application listing, interview logging, and application updates. Even the three 'attach' tools are clearly differentiated by purpose (analysis vs CV/cover letter vs interview prep). The only potential overlap between get_due and get_planned is explicitly resolved in the descriptions.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (add_application, get_application, list_applications, update_application, attach_analysis, log_interview, etc.). The verb prefix accurately reflects the action, and nouns are singular for single-item operations and plural for list operations, maintaining a predictable convention.

Tool Count5/5

With 11 tools, the server is well-scoped for a job application tracking domain. Each tool covers a necessary function without redundancy, and the count is neither sparse nor overwhelming.

Completeness4/5

The tool set covers the full lifecycle of an application: create, read, list, update, plus notes, attachments, analysis, and interview logging. Minor gaps exist—there is no explicit delete or archive tool (though status updates can archive), and interviews cannot be directly updated or removed after logging—but these are workable within the existing surface.

Resources