Skip to main content
Glama

Loomivo: verified local businesses

create_request

Send a booking (kind 'book', slot 'YYYY-MM-DDTHH:MM'), order (kind 'order', items [{offer_id, qty}], fulfilment pickup|delivery) or quote request (kind 'quote', details) for the customer. The business confirms it. Ask the customer before sending.

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": {
      "slug": "<slug>",
      "kind": "<kind>",
      "customer_name": "<customer_name>",
      "customer_phone": "<customer_phone>"
    },
    "name": "create_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
slotNo
slugYes
itemsNo
addressNo
detailsNo
staff_idNo
fulfilmentNo
customer_nameYes
customer_emailNo
customer_phoneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does add genuinely useful behavior: that the business must confirm the request (so submission is not an instant confirmation) and that customer consent is required beforehand. It omits other important traits for a mutation with 11 parameters — required permissions or staff_id scoping, what happens on an invalid slot or unknown offer, idempotency/duplicate behavior, and the shape of the response.

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 tight sentences with the payload variants front-loaded and the two behavioral facts at the end; almost nothing is wasted. The heavy parenthetical packing makes the first sentence dense to parse, which costs a point, but the overall size is appropriate for the tool's scope.

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?

For a mutation tool with no annotations, no output schema, and 11 largely undocumented parameters, the description covers the core ordering logic but leaves meaningful holes: the identifying slug, the customer contact fields, address usage for delivery, staff_id, and any indication of what comes back (request id, status). Adequate but not sufficient on its own.

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 0%, so the description must compensate, and it partially does: it gives the slot format (YYYY-MM-DDTHH:MM), the nested items structure ({offer_id, qty}), the fulfilment enum values, and what 'details' means for quotes. However, six parameters (slug, customer_name, customer_phone, customer_email, address, staff_id) are never explained — notably slug, which identifies the business, and staff_id, whose role is ambiguous.

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?

The description names a specific verb ('Send') and three concrete resources (booking, order, quote request), with the discriminating field ('kind') and its allowed values spelled out. It is not tautological and clearly separates this write tool from the read-only siblings (get_request_status, get_available_times, get_business), though it does not explicitly name them.

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 by the per-kind payload sketches, so an agent can infer which kind fits a booking vs. an order vs. a quote. The sentence 'Ask the customer before sending' is a real precondition, but there is no guidance on sequencing (e.g., fetch a valid slot via get_available_times first) and no when-not-to-use or alternative-tool routing.

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