The Johns Islander — Kiawah, Seabrook and Johns Island

Every fee to buy and own

fees

Read-onlyIdempotent

The fee ledger for Kiawah, Seabrook or Johns Island: each buyer, owner and rental charge with its amount, who charges it, how sure it is (confirmed / secondary / conflicting / not published), its source and the date it was checked.

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": {
      "island": "<island>"
    },
    "name": "fees"
  }
}

Input Schema

Name	Required	Description	Default
`island`	Yes	kiawah = Kiawah Island; seabrook = Seabrook Island; johns-island = Johns Island (incl. Kiawah River)

Output Schema

Name	Required	Description
`page`	No	The ledger page
`rule`	No	How to quote unsettled lines
`lines`	No	Each fee: name, charged_by, amount, applies_to, confidence, source, checked, note
`island`	No	Island name

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context on data-confidence categories, who charges each fee, source, and checked date, though it omits permissions or rate-limit details.

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 no filler; each clause adds either scope or useful fee metadata. The size is appropriate for a simple one-parameter lookup tool.

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 read-only, one-parameter lookup with a rich schema, annotations, and output schema, the description covers scope and data quality well. It could better route agents among sibling tools, but nothing essential is missing for 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%, with the required island enum fully documented. The description mirrors the three island names but does not add syntax or meaning 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?

States a specific resource, the fee ledger for Kiawah, Seabrook, and Johns Island, and enumerates buyer, owner, and rental charges plus metadata. It is clearly more specific than the name alone, but does not explicitly distinguish itself from siblings like true_cost or estimate_range.

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: an agent can infer this is for fee lookup on the three islands. However, there is no explicit when-to-use or when-not guidance versus true_cost, estimate_range, or island_market.

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?