Skip to main content
Glama
Sign In
@godman-protocols/lax-mcp

@godman-protocols/lax-mcp

by 195440
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

lax_get_job

Fetch a LAX job's full specification, bounty amount, and acceptance criteria by ID.

Instructions

Fetch the full specification, bounty amount, and acceptance criteria for a single LAX job by ID.

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": {
      "id": "<id>"
    },
    "name": "lax_get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesJob UUID or identifier.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the payload contents (spec, bounty, acceptance criteria), but says nothing about authentication, errors, or behavior for an unknown ID. Low-risk read semantics are implied by 'Fetch' but not asserted.

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?

One sentence, front-loaded with the verb and resource, with every clause adding content (what is returned). No filler or redundancy.

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?

With no output schema, the description's enumeration of returned fields is valuable and covers the single required parameter. The remaining gap is behavioral (error/not-found handling) rather than structural.

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% and the single 'id' parameter is fully documented as a job UUID/identifier. The description's 'by ID' adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Fetch') and resource ('a single LAX job by ID'), plus the content returned (spec, bounty, acceptance criteria). The 'single ... by ID' phrasing implicitly distinguishes it from the sibling lax_list_jobs, but no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is the detail-lookup counterpart to lax_list_jobs, but the description never states when to prefer it, nor what happens on a missing/invalid ID. No alternatives are named.

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