Skip to main content
Glama
Sign In

WebinarStack

by co.webinarstack
OverviewDiscussionsAdmin

Get Webinar Summary

webinarstack.webinars.summary
Read-onlyIdempotent

Read a concise setup summary for one tenant-owned WebinarStack webinar.

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": {
      "webinarId": "<webinarId>"
    },
    "name": "webinarstack.webinars.summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
webinarIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds only that the webinar must be tenant-owned, which hints at permission scoping but says nothing about error behavior or what 'concise' omits relative to the full resource.

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?

A single front-loaded sentence with no filler. Nothing is wasted, though there is very little substance to structure.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool whose annotations cover the safety profile, this is close to adequate. However, with no output schema and no statement of what fields the 'setup summary' contains, an agent cannot anticipate the response payload.

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 0% for the single webinarId parameter, so the description carries the burden. Saying 'one tenant-owned webinar' only weakly signals that webinarId identifies a single tenant-scoped resource; it adds no format, source, or lookup guidance beyond the schema's uuid pattern.

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?

States a specific verb (Read) and resource (concise setup summary) scoped to one tenant-owned webinar. It is reasonably distinguishable from analytics_summary and setup_status by the word 'setup', though it never explicitly contrasts with them.

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

Usage Guidelines2/5

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

No guidance on when to use this versus setup_status, analytics_summary, or list. The reader must infer the selection criteria entirely from the name and the word 'summary'.

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

All WebinarStack toolsInspect
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