Samplyn

Request a Samplyn demo

request_demo

Idempotent

Send a demo request to the Samplyn team, who reply within one business day. Call this only when the person has asked to book a demo and has given their name, work email and company; never guess or invent their details. companyType is one of wholesaler, brand, private_label, other; companySize is one of 1-10, 11-50, 51-200, 200+; interests are any of develop, sell, samples, make, ship, run, cardi.

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>",
      "companyType": "<companyType>",
      "companySize": "<companySize>"
    },
    "name": "request_demo"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The person's name.
`role`	No
`email`	Yes	Their work email.
`company`	Yes	Their company.
`message`	No	Anything else, in their words. At most two links.
`interests`	No
`companySize`	Yes
`companyType`	Yes
`currentSystem`	No	What they use today.

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`demo_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the agent knows this is a non-destructive outbound write. The description adds genuinely new behavioral context: a human team replies within one business day, and fabricating details is prohibited. It does not say what happens on validation failure or whether a confirmation is returned, keeping it below a 5.

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

Conciseness4/5

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

Two tight sentences, front-loaded with the action and its SLA before the gating conditions. The enumeration of enum values duplicates the schema and is the one portion that does not earn its space, but nothing else is wasted.

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 an outbound write tool with annotations covering the safety profile and an output schema covering return values, the description supplies the essential missing pieces: eligibility gate, data-integrity rule and response expectation. Minor gaps remain around failure behavior and duplicate submissions given idempotentHint=true, but an agent can call this correctly as written.

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?

With schema coverage at 56% across 9 parameters, the description compensates partially by restating the allowed values for companyType, companySize and interests. That restatement is largely redundant with the enums already in the schema, and it says nothing about role, message or currentSystem, which carry little or no schema description. Baseline 3 is appropriate.

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 opens with a specific verb and resource: "Send a demo request to the Samplyn team." It adds the response SLA (one business day), which tells the agent this leaves the system and reaches humans. It does not explicitly contrast with the read-only siblings (get_pricing, get_faq, etc.), but the write/outbound nature is unambiguous.

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 gives an explicit precondition: call only when the person has asked to book a demo and has supplied name, work email and company. The negative rule "never guess or invent their details" is a strong, actionable constraint. It stops short of naming alternatives (e.g., routing pricing or FAQ questions to the sibling lookup tools), so it is clear context rather than full when/when-not/alternatives coverage.

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

All Samplyn 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?