Hire Solidmade

Ask Solidmade for a fixed price

request_quote

Sends Solidmade a job request on the user's behalf. Only call it after the user agrees to share their email and site link. Solidmade replies to that email from hello@solidmade.co within one business day with one fixed price and a date; nothing starts and nothing is charged until the user agrees.

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": {
      "contact_email": "<contact_email>",
      "site_url": "<site_url>",
      "what_they_need": "<what_they_need>"
    },
    "name": "request_quote"
  }
}

Input Schema

Name	Required	Description
`site_url`	Yes	Link to the store, site, workflow or file the job is about.
`contact_email`	Yes	The user's email, where Solidmade sends the price.
`what_they_need`	Yes	The job in plain words: what's broken or what should be built, any deadline.
`budget_optional`	No	Optional budget or price the user has in mind.
`service_id_optional`	No	Optional service id from list_services if one fits.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-idempotent, non-destructive call, so the bar is lower. The description still adds substantive behavior the annotations cannot convey: reply from hello@solidmade.co within one business day, one fixed price, nothing starts and nothing is charged until the user agrees.

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?

Three sentences, consequence-first ordering: what it does, the consent gate, then the outcome and no-charge guarantee. No sentence is 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 five-parameter outbound request tool with no output schema, the description covers consent, response channel and timeline, and cost safety. It stops short of failure/retry behavior or what the agent should do with the incoming quote, but nothing essential to invoking it correctly is missing.

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 every parameter including the optional budget and service_id is already documented. The description adds no format, syntax, or validation 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.

Purpose5/5

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

States a specific verb (sends) and resource (a job request to Solidmade on the user's behalf), and the title pins down the outcome as a fixed price. It is unmistakably distinct from the read-only siblings get_service and list_services.

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?

Gives an explicit precondition: 'Only call it after the user agrees to share their email and site link.' That is real gating guidance, though it never names the sibling workflow (browse with list_services first, reference service_id) that naturally precedes this call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hire Solidmade tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?