Skip to main content
Glama

Lalawe — GTA events

Submit an event

submit_event

Send an in-person event in the Greater Toronto Area to Lalawe's review queue. Requirements, all checked: the event happens in person in the GTA (Toronto, Peel, York, Durham or Halton region); it hasn't ended (Toronto time); the title and description are given in BOTH English (title, description) and Simplified Chinese (title_zh, description_zh) — translate them yourself, faithfully, before calling. A person reviews it before it appears on lalawe.com. Returns a submission id; problems come back as a list to fix and resend. Limits: one call every 15s, 20 per day.

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": {
      "title": "<title>",
      "title_zh": "<title_zh>",
      "description": "<description>",
      "description_zh": "<description_zh>",
      "date": "<date>",
      "city": "<city>",
      "venue": "<venue>",
      "address": "<address>",
      "in_person": "<in_person>",
      "contact_email": "<contact_email>"
    },
    "name": "submit_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge range, e.g. "All ages", "19+", "3–12".
cityYesGTA municipality, e.g. Toronto, North York, Scarborough, Markham, Richmond Hill, Vaughan, Mississauga, Brampton, Oakville.
dateYesStart date, YYYY-MM-DD (Toronto local).
noteNoAnything the reviewer should know (not published).
priceNoPrice as shown to attendees, e.g. "$15, kids free".
titleYesEvent name in English (as the organizer writes it, no date in it).
venueYesVenue name.
addressYesStreet address, ideally with postal code.
is_freeNotrue if free to attend, false if paid. Omit if unknown.
categoryNoOne category.
end_dateNoLast day for a multi-day event, YYYY-MM-DD. Omit for a one-day event.
end_timeNoEnd time, 24-hour HH:MM. Omit if unknown.
title_zhYesEvent name in Simplified Chinese.
event_urlNoThe organizer's own page for this event (http/https).
image_urlNoA poster or photo of the event (http/https, jpg/png/webp).
in_personYesMust be true: the event happens in person (not online).
start_timeNoStart time, 24-hour HH:MM, Toronto local. Omit if unknown.
ticket_urlNoWhere to buy tickets / register (http/https).
descriptionYesWhat it is, who it's for, what to expect — in English, a few sentences, plain text.
contact_nameNoSubmitter or organizer name (not published).
contact_emailYesHow the reviewer can reach the submitter (not published).
description_zhYesThe same description in Simplified Chinese.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations, the description discloses human review before publication, return of a submission id, error responses as a fixable list, and explicit rate limits of one call every 15 seconds and 20 per day. These are material behavioral details an agent needs before calling.

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?

The description is front-loaded with the action and scope, then lists requirements and operational limits efficiently. It is dense but almost every clause carries necessary eligibility or behavior information.

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?

For a 22-parameter submission tool with no output schema, the description covers purpose, eligibility, bilingual content requirements, review flow, return value, error handling, and rate limits. The input schema already documents individual fields, so there are no major gaps.

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?

Schema coverage is 100%, so the baseline is 3. The description earns extra credit by adding a requirement not obvious from field descriptions alone: the English and Simplified Chinese title and description must both be supplied, and the agent must translate them faithfully before calling.

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 states a specific verb and resource: sending an in-person GTA event to Lalawe's review queue. It is clear what the tool does, but it does not explicitly differentiate itself from the sibling check_submission tool.

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 strong eligibility conditions: in-person in the GTA, not yet ended, and bilingual English/Simplified Chinese content. The exclusions are implied by those requirements, but no alternative tool or follow-up path such as check_submission is named.

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