Skip to main content
Glama

Modulos AI Governance Platform

request_demo

Destructive

Submits an open demo request without picking a specific time. Use this when the user does not want to choose a slot — the Modulos team will reach out within 1 business day.

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": {
      "name": "<name>",
      "email": "<email>",
      "company": "<company>"
    },
    "name": "request_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailYes
companyYes
messageNoContext: use case, urgency, frameworks of interest (EU AI Act, ISO 42001, NIST AI RMF).
job_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / 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.1/5.0
Behavior4/5

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

Annotations already declare the write/external/non-idempotent profile, so the description's job is to add context, and it does: it discloses the outbound human follow-up and a concrete response commitment ('the Modulos team will reach out within 1 business day'). It does not mention that no immediate confirmation or cancellation path exists, which is the main remaining gap.

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?

Two short sentences, zero filler, with the differentiating constraint front-loaded before the follow-up expectation. Every sentence carries distinct 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?

For a simple submission form with no output schema, the description gives enough to act: what it does, when to pick it, and what happens after submit. Missing only confirmation/timing-until-submission details and any hint at the required fields.

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

Parameters2/5

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

Schema description coverage is only 20% (just 'message'), and the description adds nothing about the required fields (name, email, company) or the undocumented job_title. For a 5-parameter tool with thin schema docs, the description should carry more of this burden and does not.

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 ('Submits an open demo request') plus the defining scope constraint ('without picking a specific time'), which cleanly separates it from book_demo_slot without naming it.

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 selection condition: use this when the user does not want to choose a slot. The alternative (booking a specific slot) is implied by the negation rather than named, so it stops just short of full routing 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