Skip to main content
Glama

Community launch readiness test — should you start a local meetup?

assess_community_launch_readiness
Read-onlyIdempotent

Answers 'should I start an engineering-leadership meetup in my city?' using ELC's own new-city launch playbook (the real doc used to launch Brno, Bratislava and Kraków) as the checklist: speaker network, promo channels, a named local operator, realistic first-event targets, and a promo budget. Call without answers to get the 5 questions; call with all 5 to get a verdict plus the specific open gaps.

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

Input Schema

NameRequiredDescriptionDefault
answersNoAnswers keyed by dimension id, true/false. Valid keys: speaker_network, promo_channels, local_operator, realistic_targets, promo_budget. Omit to receive the 5 questions first.
contextNoOptional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "report": {
      -      "description": "The full human-readable report.",
      -      "type": "string"
      -    },
      -    "source": {
      -      "description": "Canonical engineeringleaders.io page this answer is derived from.",
      -      "type": "string"
      -    },
      -    "verdict": {
      -      "description": "Headline verdict, when the tool returns one.",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "report",
      -    "source"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Changed2 schema fields changed
    • addedInput schema / properties / answers / additionalProperties / anyOf
      Added value: +[
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "string"
      +  }
      +]
    • removedInput schema / properties / answers / additionalProperties / type
      Removed value: -"boolean"
  3. Changed2 schema fields changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer."
    • removedInput schema / required
      Removed value: -[
      -  "context"
      -]
  4. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "context"
      +]
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the description's job is lighter; it still adds real value by disclosing the two-step question-then-verdict pattern and the provenance of the checklist (the real doc used for Brno, Bratislava and Kraków). The one gap is that behavior with partial answers is not specified.

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?

The description is a tight, front-loaded statement: the question it answers comes first, then the checklist source, then the call behavior. No sentence is padding and the parenthetical provenance earns its space by justifying why the checklist is credible.

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?

Given the nested answers object, the two-step interaction, and the absence of an output schema, the description is largely complete: it enumerates the dimensions and promises a verdict plus specific open gaps. It leaves the partial-answer case undefined, which is the main missing piece for correct invocation.

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 coverage is 100% and the schema already explains that omitting answers returns the five questions and documents the valid dimension keys. The description's only addition is that all five are needed for a verdict, which is marginally useful, but it does not explain what happens with partial answers or how the optional context field is used.

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 states the exact question it answers ('should I start an engineering-leadership meetup in my city?') and the mechanism (ELC's new-city launch playbook checklist) with its five named dimensions. This is unmistakably distinct from the sibling assessment tools like benchmark_leadership_ratio or plan_leadership_career_path.

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 explicit invocation guidance for both modes: call empty to retrieve the five questions, call with all five answers to receive a verdict plus gaps. There is no discussion of when not to use it or what to do with partial answers, so it stops short of full 5-level 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.