The Johns Islander — Kiawah, Seabrook and Johns Island

Island meetings: town, City and County councils

meetings

Read-onlyIdempotent

The public meetings that decide things on the islands — Kiawah Island Town Council, Seabrook Island Town Council, Charleston City Council and Charleston County Council: every date the body itself has posted, with the time, the place, the agenda once it posts, and each body's stated schedule and agendas page. Dates are never worked out from a pattern; a body that posts none (the County) gives its schedule and its meetings site instead.

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

Input Schema

Name	Required	Description	Default
`body`	No	kiawah-council = Kiawah Island Town Council; kiawah-planning = Kiawah Island Planning Commission; kiawah-bza = Kiawah Island Board of Zoning Appeals; seabrook-council = Seabrook Island Town Council; city-council = Charleston City Council; county-council = Charleston County Council

Output Schema

Name	Required	Description
`page`	No	The meetings page
`as_of`	No	The islands' date
`bodies`	No	Each body: name, covers, when it meets (its own words), where, agendas, watch, source
`checked`	No	When the schedules were read
`calendar`	No	A calendar feed of every meeting
`meetings`	No	Each posted meeting from today on: body, kind, date, time, where, agenda, packet, our_story
`recently_held`	No	The last 30 days: minutes when posted, agenda, our story

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / meetings / description

Previous value: -"Each posted meeting from today on: body, kind, date, time, where, agenda, packet"New value: +"Each posted meeting from today on: body, kind, date, time, where, agenda, packet, our_story"

addedOutput schema / properties / recently_held

Added value: +{
+  "description": "The last 30 days: minutes when posted, agenda, our story"
+}

AddedNov 3, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare a read-only, idempotent, non-open-world lookup, so the description does not need to repeat safety. It adds meaningful behavior: dates are never inferred from a pattern, and for a body with no posted dates the tool returns that body's schedule and meetings site. It does not state what happens when body is omitted or how results are returned, but the output schema covers returns.

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 and reasonably compact for the scope, with the second sentence adding a non-obvious caveat. The body list is somewhat long but useful; no major filler.

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?

For a one-param lookup with an output schema and full annotations, the description covers scope, included fields, and the County exception well. The remaining gap is the unspecified default when body is omitted, so it is strong but not fully complete.

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 sole optional body parameter already has a full enum description for all six values. The prose mentions bodies but adds no syntax, default, or selection semantics beyond the schema.

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 the resource and scope precisely: public island meetings for four named bodies, including dates, times, places, agendas, schedules, and pages. It is clear this returns meeting information, though it does not explicitly contrast itself with a sibling such as happenings.

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

Usage Guidelines3/5

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

Usage is implied by 'public meetings that decide things on the islands' and the listed bodies, but there is no explicit when-to-use/when-not guidance or named alternative. The County exception explains output behavior rather than tool selection.

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

All The Johns Islander — Kiawah, Seabrook and Johns Island tools Inspect

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

Need Help?