Skip to main content
Glama

Free trial details

get_trial_info
Read-onlyIdempotent

Describe the free SentinelOne trial (2 licenses for 14 days, no card required) and return the sign-up URL. The person completes the sign-up and SMS verification themselves.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trial_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
daysYes
productNo
licensesYes
trial_urlYes
after_trialNo
verificationNo
card_requiredNo

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 already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond those: the tool returns a sign-up URL and the human-in-the-loop SMS verification step is out of the agent's hands, which prevents the agent from pretending to complete enrollment. It does not discuss trial eligibility or regional limits, keeping it a 4 rather than 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.

Conciseness5/5

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

Two sentences, both front-loaded and load-bearing: the first gives the offer terms and return artifact, the second gives the responsibility boundary. No filler, no restating of the title.

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 an output schema present, return values need no explanation, and the description covers the offer terms, the sign-up URL, and who completes enrollment — sufficient for a zero-parameter informational tool. Minor gaps remain around eligibility or what to do if the user cannot sign up, but nothing needed to invoke it correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning for the description to compensate for. The schema is empty and fully specified with additionalProperties=false, leaving nothing ambiguous.

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 names a specific verb (describe) and resource (free SentinelOne trial) and states the concrete terms returned: 2 licenses, 14 days, no card required. It also delimits scope by noting the caller only gets details plus a sign-up URL, which cleanly separates it from transactional siblings like build_quote or request_quote.

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?

The context is clear — this is the informational path for trial questions — and the second sentence gives an explicit boundary: the person completes sign-up and SMS verification themselves, so the agent must not attempt it. It stops short of naming a specific sibling alternative for users who instead want to purchase or quote, so it is strong but not fully explicit 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