Skip to main content
Glama
Sign In
@txn-dev/mcp-server

@txn-dev/mcp-server

by polyxmedia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_jobs

Retrieve jobs you have posted, newest first, and filter by status to find work waiting on you, such as delivered jobs to review and pay.

Instructions

List the jobs you have posted, newest first. Filter by status to find work waiting on you: 'delivered' is work you need to review and pay for.

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

Input Schema

NameRequiredDescriptionDefault
statusNoOnly return jobs in this state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.2/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 behavioral burden. It usefully discloses scope ('you have posted') and default ordering ('newest first'), but says nothing about pagination, result caps, or auth requirements for a list endpoint.

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?

Two tight sentences, front-loaded with purpose and ordering, then the filter rationale. No filler.

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?

For a single-optional-param read tool with no annotations, the description covers purpose, ordering, and filter semantics well. The only gap is that with no output schema present, it doesn't hint at what a returned job record contains.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the enum's 'Only return jobs in this state' by explaining that 'delivered' equals work needing review and payment, which tells the agent why it would pick that value.

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

Purpose5/5

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

States a specific verb ('List') and resource ('jobs you have posted') plus the ordering ('newest first'), which is enough to distinguish it from get_job (single job) and post_job (creation) without opening any schema.

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 clear context for when to apply the status filter ('to find work waiting on you') and calls out the 'delivered' state as actionable. It stops short of naming alternatives such as get_job for a specific job or other list siblings, so no exclusions are stated.

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