Skip to main content
Glama

TexContractor

List open homeowner job requests (for pros)

list_open_job_requests
Read-onlyIdempotent

For contractors and pros: open job requests that homeowners posted on TexContractor, optionally filtered by state, city or service. Pros list their service free to send offers. No lead fees.

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_open_job_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo
stateNo
serviceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety is covered. The description adds business context (no lead fees) but says nothing about pagination behavior, default/maximum result window, or what an entry contains beyond the filter axis.

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?

Front-loaded with the core scope and filter capability in one sentence. The trailing two sentences ('Pros list their service free to send offers. No lead fees.') are marketing copy that does not help an agent select or invoke the tool and could be cut.

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 simple, zero-required-param read tool with no output schema and strong annotations, this is close to sufficient — the optional filtering and audience are clear. The remaining gap is paging/result-set behavior and value formats for the filter parameters.

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 description must carry the burden, yet it only maps a filter intent onto city, state and service without explaining expected formats (state abbreviations? service names aligned with list_services?). The 'limit' parameter is never mentioned or its 1-20 / default 10 semantics clarified.

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+resource: open job requests posted by homeowners on TexContractor, with an audience qualifier ('for contractors and pros'). It is clearly distinguishable from post_job_request or find_local_pros by resource, though it never names a sibling to route against 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?

Establishes audience ('for contractors and pros') and implies usage when looking for open jobs to bid on, but gives no when-not-to-use guidance or pointer to alternatives such as find_local_pros. The 'free to send offers / no lead fees' sentences are promotional rather than decisional.

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