Skip to main content
Glama

Zain Saeed: hire a web developer

Send a quote request to Zain

request_quote

Emails the user's name, email address and project details to Zain so he can reply with a fixed-price quote, usually within 24 hours. The request goes only to Zain and is used only to reply to it.

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": {
      "name": "<name>",
      "email": "<email>",
      "project": "<project>"
    },
    "name": "request_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's name.
emailYesEmail address Zain should reply to.
budgetNoOptional. Budget, for example "$3,000 - $5,000".
companyNoOptional. Company name.
projectYesWhat they need built or fixed, in a few sentences.
serviceNoOptional. Closest service, for example "Shopify development".
websiteNoOptional. Their current website URL.
timelineNoOptional. When they need it, for example "within 4 weeks".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and non-idempotency, so the safety profile is covered. The description earns credit by adding what annotations cannot: the email goes only to Zain, is used only to reply, and typically gets an answer within 24 hours — useful context for an agent reasoning about an external, irreversible send.

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 sentences, front-loaded with the action and recipient, followed by the privacy constraint. Nothing is redundant or padded.

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 an 8-parameter outbound-email tool with no output schema, the description covers the essentials: recipient, payload, turnaround, and data-handling limits. It does not say what a successful call returns or what happens if delivery fails, which leaves a small 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?

Schema coverage is 100%, so all eight parameters, including the optional budget, company, service, website and timeline, are already documented. The description names the three required fields and characterizes project content as 'project details,' which is only marginally beyond the schema; 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?

The description uses a specific verb and resource — 'Emails the user's name, email address and project details to Zain' — and states the outcome (a fixed-price quote reply). It is unmistakably distinct from the read-only siblings (get_profile, list_case_studies, list_services) because the agent sees this sends an outbound email rather than fetching data.

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?

Usage is implied: this is the tool that initiates a quote conversation with Zain. The description adds a data-use constraint ('used only to reply to it') and an expectation ('usually within 24 hours'), but it never says when to prefer it over a sibling or when not to call it, such as only after the user has agreed to be contacted.

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.