Skip to main content
Glama

How a business trains Emma

how_to_train_emma
Read-onlyIdempotent

How a business owner teaches Emma: catalog learned and updated every day, business information written to Emma on WhatsApp (opening hours, shipping, returns, offers), corrections, Conversations and "Hand back to Emma", step-by-step guide. 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": "how_to_train_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.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower. The description still adds real context: no key is required and the response is an automated text generated by Emma rather than a static article, which is behavior an agent cannot read off the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense sentence with the topic front-loaded, so it is not padded, but the mid-sentence list of covered topics ('opening hours, shipping, returns, offers') is loosely structured and the trailing 'Read-only, no key. The answer is an automated text...' fragments interrupt the flow.

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 return values need not be spelled out, and annotations cover the safety profile. For a one-optional-param reference tool the coverage of topics and the 'no key / AI-generated answer' note are sufficient; only the language parameter's effect is unaddressed.

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% for the single optional 'language' enum (en/fr/de) with a default, so the schema already carries the semantics. The description never mentions language or how it affects the returned guide, so it adds nothing beyond the schema; baseline 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 makes clear this returns instructional content: a step-by-step guide on how a business owner teaches Emma (catalog updates, business info sent over WhatsApp, corrections, Conversations/hand-back). It is a specific resource even though the verb ('returns a guide') is only implied, and it implicitly separates itself from conversational siblings by stating 'the answer is an automated text from Emma, an AI.'

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: an agent can infer this is the how-to/onboarding reference as opposed to talk_to_emma or about_emma. There is no explicit when-to-use vs when-not-to-use guidance and no mention of the other sibling tools, so the agent must infer the routing.

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