Skip to main content
Glama

Job Logs

job_logs
Read-only

Retrieve recent log lines for a background job using its job ID and optional tail limit to diagnose progress or failures.

Instructions

Recent log lines for a background job.

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": "job_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNo
job_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered, and an output schema exists so return structure need not be described. The description adds only the word 'recent', which implies a recency window but never states how far back it reaches or whether output is paginated. Minimal added value beyond structured fields.

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?

A single short sentence, front-loaded and free of filler, so nothing is wasted. Its brevity is close to under-specification rather than true conciseness, but structurally it is clean.

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?

With an output schema and read-only annotations already covering returns and safety, the definition still leaves both parameters unexplained and gives no usage context. For a tool whose entire behavior hinges on how many lines 'recent' means, this is too thin.

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?

Schema description coverage is 0%, so the schema provides no meaning for job_id or tail, and the description does not compensate: it never explains that tail controls line count or that the default is 100. Only the vague word 'recent' gestures at the tail parameter's purpose.

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

Purpose3/5

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

The phrase 'Recent log lines for a background job' names a specific resource (log lines) and scope (recent, per-job), so the agent can tell it returns log output rather than job status. However, it is a bare noun phrase with no verb and no explicit differentiation from the sibling job_status tool, leaving the boundary between logs and status to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus job_status or any other sibling, and no prerequisites or exclusions are given. The agent must infer that this is for troubleshooting output rather than checking job state.

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