Skip to main content
Glama

Job draft check

job_draft_check
Read-onlyIdempotent

Checks a proposed job and returns problems with a fix hint. Nothing is saved, sent, or announced. Read only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_draft_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
townNo
whenNo
titleNo
effortNo
summaryNo
provinceNo
remote_okNo
contact_viaNo
compensationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context by stating that nothing is saved, sent, or announced, and that the return includes problems with a fix hint. It does not cover authentication, rate limits, or failure modes, so it falls short of a 5.

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?

The description is three short sentences and the key validation purpose is front-loaded. Every sentence adds either purpose or side-effect information, with no wasted wording.

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 tool with 10 parameters, a nested object, and no output schema, the description is too thin. It adequately discloses the read-only, no-side-effect behavior, but it leaves parameter semantics and the shape of returned problems largely unexplained.

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?

There are 10 parameters with 0% schema description coverage, including a nested 'when' object, yet the description provides no field-level guidance. 'Proposed job' only vaguely indicates the input domain and does not explain what kind, town, title, effort, compensation, or the nested time fields mean or require.

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?

The description states a specific verb and resource: it checks a proposed job and returns problems with a fix hint. It is clear what the tool does, though it does not explicitly distinguish itself from related sibling tools such as jobs_board.

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?

The phrase 'proposed job' implies the tool should be used during drafting or pre-submission validation. However, the description gives no explicit when-to-use guidance, prerequisites, or named alternatives for comparison.

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