Skip to main content
Glama

Atom XII

Send Atom XII an inquiry

send_inquiry
Idempotent

Send Atom XII a question, partnership proposal or other inquiry on behalf of a person (intent field). Set consent to true only if the person agreed to be contacted. A person on the team answers; nothing is emailed automatically.

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": {
      "intent": "<intent>",
      "need": "<need>",
      "contact": "<contact>",
      "consent": "<consent>",
      "on_behalf_of": "<on_behalf_of>"
    },
    "name": "send_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the person needs, in their words: the problem, scope, roles or volumes.
testNoTrue to test an integration: recorded and marked as a test, nobody follows up.
agentNoThe agent sending this (optional but recommended). The User-Agent header is recorded too.
budgetNoBudget or range, free text (e.g. "$20k-30k a month").
intentYesWhat the person wants: a quote, a call, an answer, a partnership, or other.
companyNoThe organization the person represents.
consentYesTrue only if the person named in contact agreed to be contacted by this company about this inquiry.
contactYesThe person to answer. An email or a phone is required.
languageNoLanguage for the answer.
timelineNoWhen they want to start or decide.
on_behalf_ofYesWho the agent acts for: the person and, if any, their organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds real value by explaining the delivery model ('A person on the team answers; nothing is emailed automatically') and the consent constraint, but says nothing about latency, whether submissions can be withdrawn, or what a caller gets back on success or failure.

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 sends, the consent precondition, and what happens after submission. The key constraint and the human-follow-up fact are front-loaded where an agent will see them.

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 11-parameter submission tool with nested objects, no output schema and annotations already covering mutability, the description is nearly complete: it conveys who sends, what is sent, the consent rule and the non-automated follow-up. The only gap is the absence of any guidance on the request_quote/book_call overlap or on what a submission returns.

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 100%, so all 11 parameters, including the nested contact and agent objects, are already documented in the schema. The description reinforces the intent and consent fields but adds no format, constraint or example detail beyond what the schema states; baseline 3 applies.

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?

States a specific verb ('Send') and resource ('an inquiry to Atom XII') and enumerates the inquiry kinds (question, partnership proposal, other) via the intent field. It does not differentiate from siblings like request_quote or book_call, even though the intent enum overlaps with those tool names, so an agent could be unsure which entry point to use.

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?

Provides one concrete conditional ('Set consent to true only if the person agreed to be contacted'), which is genuine usage guidance for the riskiest field. However, it never says when to prefer this tool over request_quote or book_call, and gives no when-not-to-use or prerequisite context beyond consent.

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