ALICE - Palm Coast Local

Ask ALICE (Palm Coast Local)

ask_alice

Read-onlyIdempotent

Ask ALICE, Palm Coast Local's AI guide, about Palm Coast and Flagler County, Florida.

Covers local businesses and services (plumbers, HVAC, doctors, restaurants, hotels...),
upcoming events, deals, schools, golf, beaches, government and community information.
Multi-part questions work ("going to the fall festival and want dinner after").
Returns ALICE's own answer plus the matching Palm Coast Local listings with phone,
address, hours and page links.

Args:
    question: The visitor's question in plain language.

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": {
      "question": "<question>"
    },
    "name": "ask_alice"
  }
}

Input Schema

Name	Required	Description	Default
`question`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), so the lower bar is met, and the description still adds real behavioral information: it discloses that the reply contains both a generated answer and matching directory listings with phone, address, hours, and links. It does not discuss answer latency, fallback behavior when nothing matches, or accuracy caveats for AI-generated content.

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?

It is front-loaded with the identity and scope, then the capability list, then the return shape, and every sentence adds something. The 'Args:' block is slightly redundant given a single self-explanatory parameter, but no sentence is wasted.

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 single-parameter read-only query tool with an output schema, this covers purpose, scope, phrasing guidance, and return shape. The only meaningful gap is the absent relationship to the local_news sibling, which would help an agent route between the two.

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?

With only one parameter and 0% schema description coverage, the description must carry the weight, and it does: 'the visitor's question in plain language' plus the multi-part example tells the agent how to phrase input rather than passing structured filters. The guidance is short but sufficient for a single free-text field.

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 opening sentence names the specific agent (ALICE, an AI guide) and its exact geographic domain (Palm Coast and Flagler County, Florida). The coverage list that follows (businesses, events, deals, schools, golf, beaches, government) removes any ambiguity about what kinds of questions are in scope, and it distinguishes the tool from the only sibling, local_news.

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?

Usage context is clear: natural-language local questions, with an explicit note that multi-part questions work and a concrete example of one. It stops short of naming conditions for choosing an alternative (e.g., when to prefer local_news for news), so it is a clear context without exclusions.

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

All ALICE - Palm Coast Local 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?