Skip to main content
Glama

TexContractor

Get a link to post a job request

post_job_request
Read-onlyIdempotent

Returns a TexContractor link where the homeowner posts their job (description, city, photos) so nearby pros contact them. Set urgent=true for BOOM: the job is sent straight to pros near them right away and stays open 24 hours. The homeowner signs in with their phone; nothing is posted until they confirm.

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": {
      "service": "<service>"
    },
    "name": "post_job_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
stateNoTX
urgentNotrue if they need help today
serviceYes
descriptionNoShort description of the problem

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Adds real context beyond the readOnly/idempotent annotations: the two-phase flow (nothing is posted until the homeowner confirms, phone sign-in required) explains why a non-destructive read tool produces a posting link. Urgent mode behavior (sent immediately, open 24 hours) is also disclosed. Missing only link expiry or reuse semantics.

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?

Three sentences, front-loaded with the core behavior. Mostly efficient, though the marketing 'BOOM' framing is slightly informal for an API description and the photos mention adds noise rather than clarity.

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?

The two-phase flow and urgent mode make the tool understandable for a mutation-adjacent operation with no output schema. However, with only 40% schema coverage, leaving the single required parameter 'service' unexplained and mentioning a non-existent 'photos' parameter leaves a real gap.

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?

Adds meaning for urgent beyond the schema's short note, and explains what the homeowner supplies (description, city). But schema coverage is 40%, and the required 'service' parameter is never explained, while 'photos' is described even though it is not an input parameter.

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 and resource: it returns a TexContractor link where the homeowner posts a job, and names the downstream effect (nearby pros contact them). This is clearly distinct from the list/find siblings, though it never explicitly says so.

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?

Gives one concrete conditional: set urgent=true when the homeowner needs help today, with the consequence spelled out. It offers no explicit when-to-use guidance versus list_open_job_requests or find_local_pros, and no stated prerequisites beyond the phone sign-in.

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