Skip to main content
Glama

Modulos AI Governance Platform

book_demo_slot

Destructive

Books a specific demo time slot. startTime must be an ISO-8601 string returned by list_demo_slots. Returns a confirmation on success.

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": {
      "startTime": "<startTime>",
      "attendeeName": "<attendeeName>",
      "attendeeEmail": "<attendeeEmail>",
      "company": "<company>"
    },
    "name": "book_demo_slot"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany or organization name.
messageNoOptional context about what the attendee wants to discuss (use case, framework, team size).
startTimeYesISO-8601 UTC start time of the slot to book, exactly as returned by list_demo_slots.
attendeeNameYesFull name of the attendee.
attendeeEmailYesBusiness email of the attendee.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / attendeeEmail / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Added
  3. Removed
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare the mutation profile: readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds that it returns a confirmation on success, but it does not explain destructive consequences, idempotency behavior, authorization needs, or failure modes; with annotations covering safety, a 3 is appropriate.

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 short sentences front-load the purpose and prerequisite with no filler. The success-return note is useful because no output schema exists.

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 a mutation booking tool with rich annotations and full schema coverage, the description covers purpose, startTime source, and success return. It omits failure behavior and explicit side-effect consequences, which keeps it from a 5.

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 schema already documents all five parameters, including the ISO-8601 startTime format and attendee fields. The description only restates the startTime sourcing constraint, so the baseline 3 applies.

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?

The description states a specific verb, 'Books,' and resource, 'a specific demo time slot,' and ties startTime to list_demo_slots. This makes the action distinguishable from slot-listing and other demo-related siblings.

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?

It establishes a clear prerequisite: startTime must be an ISO-8601 string returned by list_demo_slots, telling the agent to list slots first. It does not explicitly exclude alternatives such as request_demo or describe when not to use this tool, so it falls short of full explicit guidance.

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