Cuevr

Prepare a demo request link

demander_demo

Read-onlyIdempotent

Returns a link to the demo request form, prefilled with the details given. Use it outside the browser when the buyer wants a demo or to talk to the team. Opening the link shows the filled form: the person, or their browser agent, sends it, then the person picks and confirms the time slot in the calendar. Sends nothing by itself. To try the product alone, use demarrer_essai.

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": {
      "langue": "<langue>"
    },
    "name": "demander_demo"
  }
}

Input Schema

Name	Required	Description
`nom`	No	Last name of the person.
`email`	No	Work email address of the person. Personal mailboxes (Gmail, Outlook, Yahoo…) are refused.
`langue`	Yes	Language of the buyer's question (en, fr, es): always pass it, the pages and answers are in this language.
`prenom`	No	First name of the person.
`societe`	No	Company of the person.
`telephone`	No	Phone number of the person (optional).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 18, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the key behavioral trait that the tool 'Sends nothing by itself' and describes the downstream human flow (link opens a prefilled form, person confirms a slot). This prevents an agent from assuming the request is submitted on its behalf.

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?

Four short sentences, front-loaded with the return value, then usage, then behavioral flow, then the alternative. Every sentence carries distinct information and none repeats the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 still characterizes the return value (a link), and it covers safety behavior, intended context, and the alternative tool. Nothing an agent needs to call it correctly is missing.

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% with maxLength, enum, and per-field docs already in the schema, so the baseline is 3. The description only adds the general notion of 'prefilled with the details given' and no per-parameter syntax or format guidance beyond that.

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 ('Returns a link to the demo request form, prefilled with the details given'), which tells an agent exactly what the tool produces. It also names the sibling demarrer_essai as the alternative, so the tool is distinguishable without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit use context ('Use it outside the browser when the buyer wants a demo or to talk to the team') and names the alternative path for a different intent ('To try the product alone, use demarrer_essai'). The agent knows both when to select it and when to route elsewhere.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cuevr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?