Skip to main content
Glama

muslimtasker_quote_request

[$0.01 USDC per call via x402] Request a home-service quote from MuslimTasker (ID-verified local taskers for plumbing, electrical, handyman, cleaning, moving, repairs, remodels; United States and Canada). Submit the customer's full contact details and the job; MuslimTasker contacts the customer directly, usually within 1 business day, with a quote. Incomplete submissions return 400 with the missing fields and are not charged. REFERRAL BOUNTY: when a contractor accepts the lead, the wallet that paid for this call earns $10 USDC (paid weekly); check /api/muslimtasker/status for bounty status.

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": {
      "customer_name": "<customer_name>",
      "customer_email": "<customer_email>",
      "customer_phone": "<customer_phone>",
      "address": "<address>",
      "city": "<city>",
      "state": "<state>",
      "zip": "<zip>",
      "task": "<task>",
      "customer_consent": "<customer_consent>"
    },
    "name": "muslimtasker_quote_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesZIP or postal code
cityYesCity
taskYesDetailed description of the job (what, where in the home, what is broken, sizes, materials), at least 20 characters
notesNoAnything else: gate codes, pets, parking, photos (URLs), access instructions
stateYesState or province, e.g. FL
budgetNoCustomer's budget or expectation, e.g. '$150-250' or 'needs quote'
addressYesStreet address where the work is needed (house/apartment number and street)
countryNoUS or CA (default US)
urgencyNoemergency (same day), urgent (within 48 h), normal (default), flexible
categoryNoService category: plumbing, electrical, handyman, cleaning, moving, furniture-assembly, tv-mounting, painting, yard-work, appliance-repair, hvac, roofing, remodel, general-contracting, emergency-repair, other (default: other)
agent_nameNoName of the AI agent or platform submitting the request
callback_urlNoOptional https URL; MuslimTasker POSTs a JSON status update to it whenever the lead status changes
agent_contactNoEmail or URL where MuslimTasker can reach the agent operator
customer_nameYesCustomer's full name (as they want to be addressed)
customer_emailYesCustomer's email address (MuslimTasker will send the quote here)
customer_phoneYesCustomer's phone number with country code, e.g. +1 407 555 0100 (MuslimTasker will call or text)
preferred_dateNoPreferred date YYYY-MM-DD, or a range/notes
preferred_timeNoPreferred time window, e.g. morning, 2-5pm, weekends
customer_consentYesMust be 'true': the customer has agreed to be contacted by MuslimTasker at the email and phone given
contact_preferenceNoHow the customer prefers to be contacted: call, text, whatsapp or email (default: call)
preferred_languageNoCustomer's preferred language, e.g. English, Arabic, Urdu (default English)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses key behavior: $0.01 USDC per call via x402, MuslimTasker contacting the customer directly within one business day, 400 errors on incomplete submissions without charge, and a $10 USDC bounty. It does not describe the successful response payload or privacy/data-retention handling.

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-loads the price and purpose, then covers workflow, error behavior, and bounty. It is dense but most sentences earn their place, though the bounty and status-check details add length.

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?

Covers service scope, cost, contact workflow, error handling, and referral status for a complex 21-parameter tool with no annotations or output schema. It leaves the successful response shape and consent/privacy handling to the schema, so it is not fully complete.

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%, so the schema already documents all 21 parameters thoroughly. The description adds only high-level context about submitting contact details and the job, without adding parameter-level meaning beyond the schema.

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 and resource: 'Request a home-service quote from MuslimTasker,' with service categories and geography. It is clearly distinguishable from muslimtasker_status, which is mentioned only for checking bounty status.

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?

Explains the submission workflow, what happens after submission, and points to /api/muslimtasker/status for bounty status. It does not explicitly state when not to use the tool or name other alternatives beyond status checking.

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