Skip to main content
Glama

Ask the academy to get in touch

create_lead

Sends the academy team a contact request with a summary of what the person wants; a team member replies by email. The person receives no automatic email. Call it ONLY when the person gave their real name, a confirmed email address and explicit consent to be contacted. Optionally name the course slugs discussed.

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": {
      "fullName": "<fullName>",
      "email": "<email>",
      "message": "<message>",
      "consent": "<consent>"
    },
    "name": "create_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en
emailYes
companyNo
consentYesTrue only when the person explicitly agreed
messageYesWhat the person wants, in their words or summarised by you
fullNameYes
courseSlugsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent, closed-world), so the description carries the real burden and does add value: the person gets no automatic email, a human replies, and the payload is a summary of intent. It does not warn that repeated calls create duplicate requests despite idempotentHint=false, which is a meaningful omission for a send action.

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?

Three sentences, no filler, and the ordering is right: what happens, what the recipient does not get, then the precondition for calling. Every clause carries operational information.

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?

With no output schema, the description usefully explains the follow-up path (human email reply) so the agent knows what to tell the user. For a 7-parameter mutation with 43% schema coverage, the gaps are the unmentioned lang/company parameters and no note on duplicate submissions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 43% schema coverage the description must compensate, and it does for most of the required set: fullName ('real name'), email ('confirmed email address'), consent ('explicit consent'), message ('summary of what the person wants'), and courseSlugs ('optionally name the course slugs discussed'). Only lang and company go unmentioned, so the compensation is good but not complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Sends the academy team a contact request') and immediately explains the outcome ('a team member replies by email'). This clearly separates it from every sibling, which are all read-only content lookups (get_course, list_trainers, search_courses), so an agent knows this is the only outbound-contact action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit, hard gate: call it ONLY when real name, confirmed email, and explicit consent are present. That is a real when/when-not rule rather than vague context. It stops short of telling the agent what to do when consent is missing (e.g., ask for it, or drop the lead), which is the one remaining inference.

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