Skip to main content
Glama

Webinar Follow-Up Capacity

bpj_webinar_followup_capacity
Read-onlyIdempotent

Convert registrations to expected attendance and qualified leads, then estimate staffing for one-day follow-up.

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": {
      "registrations": "<registrations>",
      "attend": "<attend>",
      "qualify": "<qualify>",
      "perRep": "<perRep>"
    },
    "name": "bpj_webinar_followup_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
attendYes
perRepYes
qualifyYes
registrationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=false and destructive=false, so the safety profile is fully covered and the description does not need to repeat it. The description adds genuine context beyond the annotations by disclosing the multi-stage transformation performed internally, but says nothing about rounding behavior, whether the result is fractional or ceiling-rounded, or determinism beyond what the hints imply.

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?

A single front-loaded sentence with a clear sequential verb chain and no filler; every clause maps to a stage of the computation.

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 four-required-parameter calculator with no output schema and no parameter descriptions in the schema, the definition should say what number comes back and how it is rounded or floored. It covers the pipeline conceptually but leaves the output contract and edge cases (zero registrations, 0% attendance) unaddressed.

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 0%, so the description must carry the burden, and it only partly does: 'registrations', 'expected attendance', 'qualifying as leads' and 'per representative per day' loosely map onto the four required fields. It never states that the percentages are applied multiplicatively in sequence, nor how 'attend' and 'qualify' compose or how perRep divides the lead count, leaving the actual parameter interaction to inference.

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 names a concrete computational chain (registrations -> expected attendance -> qualified leads -> staffing) for a specific domain (webinar follow-up), which is enough to tell it apart from generic capacity siblings like bpj_sprint_capacity or bpj_line_bottleneck_capacity. It stops short of stating the unit of the final answer (headcount of reps for one day), so purpose is clear but not fully pinned down.

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?

There is no explicit when-to-use statement, no preconditions (e.g., must supply percentages as whole numbers, not fractions), and no routing to or away from any alternative. The only implied guidance is the 'one-day follow-up' scope, which a caller must infer.

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.