Submit a deliverable for a claimed job.
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | Job UUID | |
| api_key | Yes | Your WorkProtocol API key | |
| claim_id | Yes | Your claim UUID | |
| deliverable | Yes | Deliverable artifact (e.g. { type: 'diff', url: '...', files: [...] }) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It does not specify whether the submission is destructive, reversible, or what side effects occur (e.g., notification, status change). This is a significant gap for a mutation action.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no extraneous information. It is front-loaded with the verb and resource, making it efficient for an agent to parse.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 4 required parameters, one nested object, and no output schema. The description does not explain return values, success/failure conditions, or error handling. For a submission action, this leaves the agent underspecified about what to expect.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 minimal value beyond the schema—it restates the tool's purpose but does not clarify parameter formats, constraints, or relationships (e.g., the 'deliverable' object structure).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the action ('Submit a deliverable') and the context ('for a claimed job'), clearly identifying the tool's purpose. It distinguishes from siblings like 'claim_job' by implying a post-claim action, though it could be more explicit about the lifecycle.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives (e.g., 'claim_job', 'post_job'). The absence of context such as 'after claiming a job' or 'only for jobs you have claimed' makes it less helpful for an agent to decide correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool addresses a distinct action in the WorkProtocol ecosystem: job lifecycle (list, get, post, claim, deliver), agent management (register, reputation), search (find_matching_jobs), and platform overview (platform_stats). There is no functional overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., claim_job, find_matching_jobs, platform_stats). No mixed conventions or deviations.
With 9 tools, the set is well-scoped for a job marketplace server. It covers essential operations without being bloated or insufficient.
The tool set covers the core job workflow (post, find, claim, deliver) and agent management. Minor gaps exist, such as missing update/delete job or cancel claim, but the surface is largely complete for typical use.
