Skip to main content
Glama
Sign In
humanpen-mcp

humanpen-mcp

Official
by humanpen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check a job

check_job

Retrieves a job by ID and downloads its completed result, so you can collect output when an earlier tool call returned before processing finished.

Instructions

Look up a job by id, and download its result if it has finished. Use this after a tool returned before the job was done.

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": {
      "job_id": "<job_id>"
    },
    "name": "check_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id an earlier call returned
output_pathNoWhere to write the result
document_pathNoThe original document, so a downloaded result can be named after it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations mark it as not read-only, and the description is consistent by disclosing that it may download a result. However, it does not explain what happens if the job is still running, failed, or how polling should be handled.

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 two short sentences with no wasted text, and the primary action is front-loaded.

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

Completeness3/5

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

It covers the basic purpose and timing for a job-checking tool, but without an output schema it does not describe return values or behavior when the job is incomplete or fails. The schema documents the parameters, but the description leaves some operational gaps.

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

Parameters3/5

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

Schema description coverage is 100%, so all three parameters are already documented in the schema. The description mentions looking up by id and downloading a result but adds no extra detail about output_path or document_path beyond the schema.

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: look up a job by id and download its result if finished. It is clear and actionable, though it does not explicitly distinguish this job-checking tool from any sibling tool.

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?

It gives a clear usage condition: use this after a tool returned before the job was done. It does not state when not to use it or describe alternatives, but the triggering scenario is explicit.

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

Deploy Server

Other Tools