Antarum

Send an inquiry to Antarum

send_inquiry

Sends the user's inquiry (buy, rent, business, advice) to the Antarum team by e-mail. Only call it after you showed the user the exact inquiry and their e-mail address and they said yes. Antarum answers by e-mail (rentals within 24 hours Monday to Friday, otherwise within 1 to 2 business days), free of charge. Returns a reference number.

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": {
      "topic": "<topic>",
      "email": "<email>",
      "message": "<message>"
    },
    "name": "send_inquiry"
  }
}

Input Schema

Name	Required	Description
`city`	No
`date`	No	Date or period, e.g. "2026-12-12" or "spring 2027".
`name`	No
`email`	Yes	The user's e-mail address for the answer.
`robot`	No	Id or name of the robot, if any.
`topic`	Yes
`company`	No
`country`	No	ISO 3166-1 alpha-2 code or name of the country.
`message`	Yes	What the user wants, in their words (at least 10 characters).
`language`	No	Language Antarum should answer in.
`quantity`	No
`share_with_partners`	No	May Antarum pass the inquiry to a matching dealer or rental firm? Ask the user. Default: false.

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?

Adds real behavior beyond the annotations: the inquiry leaves the system as an e-mail to an external team (consistent with openWorldHint=true), it is free of charge, there is a response SLA (rentals within 24h Mon–Fri, otherwise 1–2 business days), and a reference number is returned. It does not state whether repeated calls create duplicate inquiries despite idempotentHint=false, which keeps it below 5.

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 tight sentences: what it does, when it may be called, and what to expect back. The action and the confirmation gate are front-loaded, and nothing is redundant.

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 12-parameter, non-idempotent outbound action with no output schema, the description covers the essentials: side effect, consent gate, latency, cost, and return value (reference number). The remaining gap is that most optional parameters, notably the partner-sharing consent, are left entirely to the schema.

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 58% with 12 parameters, so the schema does much of the work. The description only adds meaning for topic (via the parenthetical list) and email/message (via the 'show the exact inquiry and their e-mail address' rule). It says nothing about share_with_partners, language, quantity, city, date, or the other optional fields.

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 ('the user's inquiry ... to the Antarum team by e-mail'), and enumerates the four inquiry topics (buy, rent, business, advice). The action is unmistakably an outbound contact operation, easily separated from the read-only search siblings such as search_robots or find_rental.

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 a hard precondition with a clear gate: only call after showing the user the exact inquiry and their e-mail address and receiving a 'yes'. That is genuine when-to-use guidance with an implicit exclusion. It stops short of naming alternatives (e.g. 'use find_rental to browse before sending an inquiry'), so it is not a 5.

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

All Antarum 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?