Skip to main content
Glama

Live Webinar Schedule

tt_get_webinars
Read-onlyIdempotent

Tradetron's free weekly live webinars, with the DATE of each session's next occurrence. No setup needed beyond the one-time sign-in.

Use for "when is the next webinar?", "what time is the Friday session?", "is there any free training?", "send me the webinar link". Returns both weekly sessions sorted by next occurrence, each with its day, IST start time, registration URL, and the resolved next date.

ALWAYS call this before stating a webinar date. The dates are computed server-side and are the same ones the registration pages show. Never infer "next Friday" yourself and never recall a date or a time from memory — a wrong one sends someone to a Zoom room on the wrong day. If this returns ok:false, say the sessions run weekly and give the registration pages rather than guessing.

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": "tt_get_webinars"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description goes well beyond by disclosing provenance ('computed server-side and are the same ones the registration pages show') and an explicit failure path ('If this returns ok:false, say the sessions run weekly and give the registration pages rather than guessing'). It also notes there is no setup cost beyond a one-time sign-in, which tells the agent calling it is cheap and repeatable.

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?

Structure is sensible and front-loaded: what it returns, then trigger phrases, then mandatory-call and anti-hallucination directives, then the error fallback. There is mild redundancy in 'Never infer "next Friday" yourself and never recall a date or a time from memory', which restates the ALWAYS directive in the preceding sentence, but every block still earns its place.

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 zero parameters and no output schema, the description carries the full burden and meets it: it describes the return shape field by field, states that exactly two weekly sessions come back sorted by next occurrence, and specifies what to do on ok:false. Nothing needed to invoke or report on this tool 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 add or omit. The only schema-adjacent information it supplies — that results come back sorted by next occurrence — is extra rather than redundant.

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 resource and scope: 'Tradetron's free weekly live webinars, with the DATE of each session's next occurrence.' It also enumerates the returned fields (day, IST start time, registration URL, resolved next date), so an agent knows exactly what it is fetching and cannot confuse it with the strategy/course/blog tools among its siblings.

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?

It gives concrete trigger phrases ('when is the next webinar?', 'what time is the Friday session?', 'is there any free training?', 'send me the webinar link') plus an explicit standing directive: 'ALWAYS call this before stating a webinar date.' It also prohibits the tempting alternative behavior (inferring 'next Friday' or recalling a date from memory), which is exactly the when-not guidance an agent needs.

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