Skip to main content
Glama

4fillment

Ask a person

ask_a_person

Hands the question to a person at 4fillment and returns a case reference. Use it when the user asks for a person, when ask_4fillment has no approved answer, or for money, lost or damaged stock, a price, contract or policy change, or a ship cut-off at risk. Needs the e-mail address the user wants the reply at.

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": {
      "email": "<email>",
      "category": "<category>",
      "summary": "<summary>"
    },
    "name": "ask_a_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
refsNoOrder, SKU, shipment or tracking numbers, if the user has them.
emailYesThe e-mail address the user wants the reply at. Ask the user; never invent one.
summaryYesWhat the user needs, in their words, and what was already tried. No passwords or payment details.
categoryYesshipping_at_risk or warehouse_stopped for same-day problems; receiving_or_stock, lost_or_damaged or stuck_shipment for stock and shipments; billing, integration, setup or general otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Adds context beyond the annotations by disclosing that the call creates a case and returns a reference — important since there is no output schema. Annotations already mark it as a non-read-only, non-destructive, non-idempotent operation, but the description does not warn that repeated submissions create separate cases or state the reply channel/timing.

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, front-loaded with the action and result, then escalation triggers, then the one hard input requirement. No filler and no repetition of schema detail.

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 non-idempotent escalation tool with no output schema, the description adequately covers purpose, timing and the mandatory email. It stops short of telling the agent what to do with the returned case reference (e.g., following up via get_case) or whether duplicate submissions should be avoided.

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?

With 100% schema description coverage, the schema already documents email, category, summary and the nested refs object, so baseline is 3. The description only reinforces the email requirement ('the e-mail address the user wants the reply at') and adds no meaning for the category enum or the refs identifiers beyond what the schema states.

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 action (hands the question to a person), the destination (a person at 4fillment), and the outcome (returns a case reference). It is clearly distinguishable from the sibling ask_4fillment, which it explicitly names as the self-serve alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit triggers: the user asks for a person, ask_4fillment has no approved answer, or the topic is money, lost/damaged stock, pricing, contract or policy change, or a ship cut-off at risk. The alternative and the conditions that select it are both spelled out.

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