Skip to main content
Glama

Atom Backends

Ask Atom Backends for a quote

request_quote
Idempotent

Send Atom Backends a quote request on behalf of a person. Returns an automated acknowledgement and the booking link. 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": {
      "need": "<need>",
      "contact": "<contact>",
      "consent": "<consent>",
      "on_behalf_of": "<on_behalf_of>"
    },
    "name": "request_quote"
  }
}

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").
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.8/5.0
Behavior4/5

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

Beyond the annotations (openWorldHint=true, idempotentHint=true, destructiveHint=false), the description discloses what actually happens downstream: an automated acknowledgement plus booking link is returned, a human on the team answers, and nothing is emailed automatically. That materially changes how an agent frames the action to a user. It stops short of addressing what idempotentHint=true means in practice (e.g. whether resubmitting the same request creates duplicates).

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?

Four short sentences, front-loaded with the action and the return behavior, with no filler or repetition. Every sentence contributes either purpose, return value, consent gating, or the human-follow-up fact.

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 10-parameter, nested-object write tool with no output schema, the description covers the essentials: what is sent, what comes back, that a human handles it, and the consent precondition. Minor gaps remain around the test flag and the agent identity object, though both are well described in the schema itself.

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 the schema already documents need, consent, contact, agent, budget, timeline and language in detail. The description's only added semantic is the consent condition, which largely restates the schema's own consent description and the 'on behalf of a person' framing. Baseline 3 applies when the schema carries the parameter burden.

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 opens with a specific verb and resource: 'Send Atom Backends a quote request on behalf of a person,' which tells an agent exactly what the tool does and that it acts on someone else's behalf. It does not explicitly name a sibling (e.g. send_inquiry or book_call) as the alternative, so differentiation is only implied by the 'nothing is emailed automatically' line.

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?

There is one concrete usage rule – 'Set consent to true only if the person agreed to be contacted' – which is genuinely useful gating guidance. However, the description never states when to choose this over send_inquiry, book_call, or the read-only info tools, leaving the agent to infer routing from the tool name alone.

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