Skip to main content
Glama

Atom XII

Request a call with Atom XII

book_call
Idempotent

Ask for a call with Atom XII 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 declare the mutation profile (readOnly=false, destructive=false, idempotent=true, openWorld=true), but the description adds real behavioral context beyond them: a self-service booking page is returned, a human on the team answers, and nothing is emailed automatically. The one gap is that repeated calls record requests despite idempotentHint=true — the duplicate-handling behavior is never explained.

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 with the core action and return value front-loaded, and the consent rule placed right where it matters. Minor redundancy between "recording the request" and "a person confirms a time," but nothing wasted.

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 mutation tool with nested objects and no output schema, the description covers what is created, who follows up, what is returned, and that no email is sent. Remaining gaps are duplicate-request behavior and confirmation of required contact details, which the schema largely handles.

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 parameter including nested contact/agent fields is documented structurally; the baseline applies. The description only reinforces the consent constraint ("set consent to true only if the person agreed"), which the schema's const:true and description already convey, and it adds nothing about need, on_behalf_of, or the test flag.

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+resource ("Ask for a call with Atom XII") and clarifies it is booked on behalf of a person, plus what happens downstream (a booking page is returned and the request is recorded). It is distinguishable from quote/inquiry siblings, though it never names them explicitly.

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 is implied rather than stated: the agent can infer this is for scheduling a call rather than requesting a quote or sending a generic inquiry, and the consent rule sets a precondition. There is no explicit when-to-use-this-vs-alternative guidance or statement of prerequisites such as required contact channels.

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