Skip to main content
Glama

LocationLists

by io.github.kylehawke-stack
OverviewDiscussionsAdmin

Request a new list

request_list

Ask LocationLists to add a list we do not have yet. Use it when search_datasets finds nothing that fits, or the user wants a brand, place or kind of business we do not publish. BEFORE calling: ask the user whether to send the request, and ask for their email so we can tell them when the list is ready. Pass an email only if the user gave it to you in this conversation; never guess or invent one. Called with neither email nor email_declined, it sends nothing and asks for the email. The request goes to the LocationLists team, the same place as the request box on locationlists.com. We add new datasets every day and prioritize requested ones; there is no promised date. Free, nothing is charged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe user's name, if they gave it
emailNoThe user's email, only if they gave it, so we can tell them when the list is ready
topicYesThe list the user wants, in their words (2-200 characters)
companyNoThe user's company, if they gave it
detailsNoAnything else they specified: places, fields needed (phone, website, email), timing
use_caseNoWhat they will use the list for, if they said (e.g. sales outreach, territory planning)
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. Changed3 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"The user's email, only if they chose to leave it, so we can tell them when the list is ready"New value: +"The user's email, only if they gave it, so we can tell them when the list is ready"
    • 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"
+}
    • changedInput schema / properties / topic / description
      Previous value: -"The list the user wants, in their words, e.g. \"Kubota dealers in Texas\" (2-200 characters)"New value: +"The list the user wants, in their words (2-200 characters)"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only tell the agent this is a non-idempotent, non-destructive write to an open world. The description adds real context beyond that: the request routes to the LocationLists team (same as the site's request box), there is no promised date, and the call is free with nothing charged. It also discloses the operational side effect that a call with neither email nor email_declined sends nothing and prompts for the email.

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 purpose and trigger condition are front-loaded in the first two sentences, and the pre-call checklist follows before the less critical detail about routing and cost. The final sentence ('Free, nothing is charged') is arguably redundant with the free-service framing, so it is slightly longer than strictly necessary.

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 7-parameter, non-idempotent, open-world write with no output schema, the description covers the trigger, the confirmation protocol, the data-integrity guardrail on email, and the expected side effect. The only unimplemented piece is what the agent receives back after a successful send, which is minor given the tool's request-submission nature.

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 description coverage is 100%, so every parameter including email_declined already carries its own field-level documentation. The description largely restates those rules (pass email only if given, never invent one; called with neither email nor email_declined sends nothing) rather than adding new per-parameter meaning, so the baseline of 3 applies.

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 description names a specific verb and resource ('Ask LocationLists to add a list we do not have yet') and immediately distinguishes this tool from the data-retrieval siblings by naming search_datasets as the trigger condition. An agent can tell this apart from search_datasets or buy_dataset without opening any schema.

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

Usage Guidelines5/5

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

It gives an explicit triggering condition ('when search_datasets finds nothing that fits, or the user wants a brand, place or kind of business we do not publish') and an explicit pre-call protocol: ask the user whether to send the request and ask for their email. It also states the alternative behavior when no email decision is supplied, so the agent knows what happens next.

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