Skip to main content
Glama

Atom Backends

Send Atom Backends an inquiry

send_inquiry
Idempotent

Send Atom Backends 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.7/5.0
Behavior4/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 covered. The description adds genuinely new context beyond that: a human on the team answers and nothing is emailed automatically, which tells the agent this is an asynchronous human-routed submission rather than an automated send.

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 core action and the consent constraint front-loaded, and no filler. The parenthetical '(intent field)' attached to 'on behalf of a person' is slightly confusing given that on_behalf_of is its own parameter, which costs it a point.

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 tool with nested objects and no output schema, the description covers the submission flow, the consent precondition, and what happens afterward (a human answers, no automatic email). It stops short of explaining the response the caller receives or how the test flag changes handling, though the schema documents the latter.

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 100%, including detailed field descriptions for contact, need, budget, timeline, and test, so the schema carries the burden and the baseline of 3 applies. The description only adds gloss on intent and consent, largely restating what the schema already says.

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 and resource — sending Atom Backends a question, partnership proposal, or other inquiry on behalf of a person — so the action is unambiguous. It does not distinguish itself from the sibling tools request_quote or book_call, even though the intent enum overlaps with both, leaving an agent to guess which entry point to prefer.

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?

The consent rule ('Set consent to true only if the person agreed to be contacted') functions as a prerequisite, which is useful guidance. However, there is no when-to-use versus when-not-to-use framing and no pointer to request_quote or book_call, despite those siblings covering overlapping intents.

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