Skip to main content
Glama

Atom Backends

Request a call with Atom Backends

book_call
Idempotent

Ask for a call with Atom Backends for a person. Returns the self-service booking page and records the request so a person confirms a time. 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": "book_call"
  }
}

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.
preferred_timesNoPreferred days and times, with the time zone.

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 flag this as a non-read-only, open-world, idempotent, non-destructive write; the description adds genuinely new behavior — that a request is recorded for a human to confirm a time, and that nothing is emailed automatically. It does not explain what a repeat call with the same payload does despite idempotentHint=true, which is the remaining behavioral gap.

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?

Four short sentences, front-loaded with the action and outcome, and the important caveats (human confirmation, no auto-email, consent gate) come before any detail. Minor redundancy between the consent sentence and the schema's consent description keeps it from a 5.

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 write tool with nested objects and no output schema, the description covers the essentials: what is created, what is returned (the booking page), and who follows up. It is complete enough to call correctly, with only dedupe/idempotency semantics left unstated.

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 every field including need, contact, test, budget and preferred_times is already documented in the schema. The description's consent guidance and the 'for a person' framing around on_behalf_of largely restate the schema's own consent text, so added meaning is marginal and the baseline of 3 is appropriate.

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 ('Ask for a call with Atom Backends for a person') plus the concrete outcome: a self-service booking page is returned and the request is recorded for human confirmation. The purpose is unambiguous, though it never names a sibling such as request_quote or send_inquiry to differentiate itself.

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?

Usage context is implied rather than stated: 'A person on the team answers; nothing is emailed automatically' and the consent precondition tell the agent how the flow behaves, but there is no explicit 'use this instead of X when...' routing against the other request tools. An agent must infer the boundary from the sibling names.

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