Alpha Flow Tech

Send an order request

request_order

Sends the person's order or quote request to the Alpha Flow Tech team, who reply to confirm one fixed price in writing. Nothing is charged. Only call this when the person asked for it and agreed to share their contact details.

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>",
      "need": "<need>",
      "consent": "<consent>"
    },
    "name": "request_order"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The person's name.
`need`	Yes	What they want, in their words.
`email`	No	Email to reply to (email or phone is required).
`phone`	No	Phone or WhatsApp number (email or phone is required).
`company`	No
`consent`	Yes	True only if the person agreed to be contacted by Alpha Flow Tech about this request.
`item_ids`	No	Catalogue ids they chose, if any.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare the write/open-world, non-idempotent, non-destructive profile, so the bar is lower. The description adds real context the annotations don't carry: 'Nothing is charged' and that the team replies with one fixed price in writing. It does not warn about duplicate submissions, which matters given idempotentHint=false.

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 short sentences with zero filler: what it does, what it costs, and when it may be called. The key constraint (nothing charged) is front-loaded.

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?

No output schema exists, and the description tells the agent what happens next (a written fixed-price reply), which covers the return expectation adequately. Missing details like duplicate-request behavior or response timing are minor for a 7-parameter submission tool.

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 86%, so the schema already documents nearly every field, including the consent and email-or-phone rules. The description only reinforces the consent/contact-sharing intent; it adds no format or syntax detail 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 ('Sends the person's order or quote request to the Alpha Flow Tech team') plus the outcome ('reply to confirm one fixed price in writing'). That phrasing also implicitly separates it from the sibling 'estimate' tool, which would compute rather than submit a request.

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 this when the person asked for it and agreed to share their contact details.' It says when to use but names no alternative and no when-not-to-use beyond that consent gate.

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

All Alpha Flow Tech 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?