Skip to main content
Glama

LocationLists

by io.github.kylehawke-stack
OverviewDiscussionsAdmin

Send feedback

send_feedback

Send a message to the LocationLists team: wrong or missing data in a dataset, something that did not work, a pricing question, an idea, or anything else. Ask the user before sending and use their words. Ask for their email so the team can reply, and pass it only if they gave it; never guess or invent one. Called with neither email nor email_declined, it sends nothing and asks for the email. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoThe user's email, only if they gave it
datasetNoDataset slug it concerns, if any, e.g. generac-dealers
messageYesThe feedback, in the user's words (5-4000 characters)
categoryNoWhat it is about (default other)
email_declinedNoTrue only when you asked the user for their email and they chose not to leave one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"The user's email, only if they chose to leave it"New value: +"The user's email, only if they gave it"
    • addedInput schema / properties / email_declined
      Added value: +{
+  "description": "True only when you asked the user for their email and they chose not to leave one",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare openWorld/non-readOnly/non-idempotent; the description goes well beyond by mandating user confirmation before sending, forbidding invented emails, documenting the no-op path when neither email nor email_declined is supplied, and noting the call is free.

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?

Front-loads the purpose, then layers the confirmation and email rules; each sentence carries distinct behavioral information. The first sentence's topic list is long but serves routing, so it earns its space.

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 non-idempotent outbound-message tool with no output schema, the description closes the gaps that matter: consent requirement, privacy handling of the email field, and the exact behavior of the degenerate call. Nothing needed to invoke it correctly is missing.

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, but the description adds real semantics the schema cannot: email must only be passed if the user actually gave one, and email_declined is meaningful only in relation to a missing email (neither present means nothing is sent).

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?

States a specific verb (send) and destination (the LocationLists team) plus the full range of content it accepts (bad data, breakage, pricing, ideas). It is unmistakably distinct from every sibling, which are all dataset/query/order tools.

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?

The opening list enumerates concrete triggers for use, and it adds a workflow precondition ('Ask the user before sending and use their words'). It does not name a when-not-to-use case or an alternative route, but no sibling overlaps functionally.

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

All LocationLists toolsInspect
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