Skip to main content
Glama

About Emma, the AI receptionist

about_emma
Read-onlyIdempotent

What Emma does for a small business (website chat bubble, WhatsApp, phone on the Full plan, day and night, in the customer's language, Shopify catalog with the link to buy), the public plans in USD and how to install her (Shopify, WordPress, any website). Read-only, no key. The answer is an automated text from Emma, an AI.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_emma"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoanswer language (default en)

Output Schema

NameRequiredDescriptionDefault
okYes
codeNomachine-readable reason when ok is false
textNothe answer, plain text — an automated answer from Emma, an AI
messageNowhat happened, in plain words
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, yet the description still adds useful context: no key/authentication is required, and the response is generated marketing-style prose from an AI rather than authoritative data. The latter is a real caution an agent needs, since it signals the content may be promotional and should not be treated as a verified source.

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?

The content scope is front-loaded in the first clause, followed by two short sentences covering access and answer type. The heavily nested parentheticals in the first sentence make it dense, but each listed item carries information an agent needs to judge relevance.

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?

An output schema exists, so the description does not need to explain return values, and with one optional parameter the tool is simple. What remains missing is only the routing guidance relative to how_to_train_emma and talk_to_emma, which is a modest gap for an otherwise low-complexity tool.

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% and the single optional 'language' enum is fully documented in the schema with its default. The description says nothing about language selection, so it adds no meaning beyond the schema; the baseline of 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?

The description enumerates the specific content returned: what Emma does (channels, availability, languages, Shopify catalog), public plans in USD, and installation paths (Shopify, WordPress, any site). That is a concrete informational scope rather than a restatement of the name. It stops short of naming how it differs from the sibling how_to_train_emma, so an agent must infer the boundary between 'about' and 'training' content.

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: read this when the user wants a general overview of Emma, pricing, or installation. There is no explicit when-to-use statement, no exclusions, and no mention of how_to_train_emma or talk_to_emma as alternatives, which are the most likely confusable siblings.

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