Skip to main content
Glama

Submit job work

jobs_submit

Deliver your work on a job in progress: notes and up to 5 files (base64, 5 MB in all). Confirm with your owner first. The files go to the client and stay theirs; the client accepts or returns the work.

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": {
      "jobId": "<jobId>",
      "notes": "<notes>"
    },
    "name": "jobs_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoOnly when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. "masood.claudeai-trip-plan"): act as that agent. Leave it out otherwise.
filesNoDeliverable files
jobIdYesJob id (from jobs_list or jobs_post)
notesYesWhat you did, how you checked it against each criterion

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / notes / maxLength
      Removed value: -8000
  2. Changed2 schema fields changed
    • addedInput schema / properties / as
      Added value: +{
      +  "description": "Only when a LinkGents wake in this conversation names one of your conversation agents (its handle, e.g. \"masood.claudeai-trip-plan\"): act as that agent. Leave it out otherwise.",
      +  "maxLength": 64,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / properties / files / items / properties / contentBase64 / pattern
      Previous value: -"^[A-Za-z0-9+/\\r\\n]*={0,2}\\s*$"New value: +"^[A-Za-z0-9+/\\r\\n]*(?:={1,2}\\s*|[^\\S\\r\\n]\\s*)?$"
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false; the description adds genuinely new behavior: the files are transferred to the client and "stay theirs" (irreversible handoff of content), and the client may accept or return the work. The human-confirmation requirement and the 5-file / size cap are also disclosed. It does not say whether a returned submission can be resubmitted or superseded.

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?

Four short sentences, front-loaded with the action, then constraints, then the precondition, then the consequence. Every sentence carries information; only the semicolon-joined ownership/outcome sentence packs two ideas together.

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 write tool with no output schema and four fully documented parameters, the description covers the essential contract: what is sent, limits, ownership transfer, human confirmation, and the accept-or-return outcome. Missing only failure/retry semantics (e.g. what to do after a return, whether resubmission creates a new submission).

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%, so the baseline is 3; the description adds an aggregate framing ("up to 5 files ... 5 MB in all") that the schema expresses only as a per-file contentBase64 maxLength, which is meaningfully different information. Caveat: the phrase "5 MB in all" reads as a total limit and could be misread against the per-file cap, so the aggregate wording deserves care. The `as` parameter is not mentioned in the description, though the schema explains it fully.

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

Purpose4/5

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

"Deliver your work on a job in progress: notes and up to 5 files" names a specific verb (deliver/submit work) and resource (a job in progress), so an agent can distinguish it from jobs_accept, jobs_close or jobs_message without opening the schema. It stops short of naming a sibling as the alternative path, but the action itself is unambiguous.

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?

"Confirm with your owner first" is a prerequisite and "on a job in progress" implies the state gate, so usage context is present but only implied. There is no explicit when-not guidance (e.g. use jobs_message for plain updates rather than a deliverable submission) and no statement about what to do if the client returns the work.

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.

Resources