Skip to main content
Glama

Community help: free and low-cost services, in Spanish and English

community_help
Read-onlyIdempotent

The guide's bilingual community directory: free and low-cost services for people who LIVE and WORK on the East End. Immigration legal advocacy, sliding-scale and no-status-asked clinics, food pantries, the winter shelter, tenant-rights and wage-theft hotlines, ESL / GED / citizenship classes, childcare and youth programs, money transfer, Spanish-language Mass times, the Latino markets, and the Sunday soccer. Call this for any I-need-help question — unpaid wages, eviction, a doctor without insurance, English classes, food, a lawyer for an immigration case — and for anything asked in Spanish. Answering from memory here means naming a national hotline or a legal aid society that does not serve this county, and the asker loses a day's work finding that out. Every record carries phone, source, sourceUrl and lastVerified, and the guide's own text in BOTH languages (description.es / description.en): quote the Spanish as written rather than translating the English. Two things are computed rather than stored: nextSpanishMass / nextEnglishMass, the next service from right now on the East End's clock (America/New_York) — 'today at 7:00 PM' means today here — and inSeasonNow on the soccer leagues for this month. offEastEnd: true marks a real referral to Bay Shore, Hempstead or Central Islip: still the right answer sometimes, but say the drive out loud. NEVER volunteer that a service is free, confidential, or safe regarding immigration status unless the record's own words say so — quote those verbatim where they appear and attribute them, and otherwise give the phone number. Never name a provider that is not in the results. Pass query in the asker's own words, in either language; need is a shortcut vocabulary; town takes the asker's own place words. With no argument nothing is looked up — you get the needs and towns covered, so ask. Returns up to 8.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needNoShortcut category, when the question is plainly one of these.
townNoA hamlet ('East Hampton', 'Riverhead') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words.
queryNoWhat they need, in their words and either language, e.g. 'my boss hasn't paid me', 'clases de inglés', 'food pantry', 'misa en español', 'dentist', 'help with rent'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld=false), and the description goes well beyond them: computed fields (nextSpanishMass/nextEnglishMass, inSeasonNow), the meaning of offEastEnd, the 'returns up to 8' limit, and hard behavioral rules about never asserting free/confidential/status-safe and never naming providers not in the results.

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-loaded with purpose and usage before the data/behavioral detail, and almost every sentence carries operational weight. It is dense and long, but the length is justified by the tool's complexity and the verbatim-quoting/never-volunteer rules.

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?

With no output schema, the description carries the return-shape burden and does: it names the per-record fields (phone, source, sourceUrl, lastVerified, description.es/en), the two computed fields, the offEastEnd marker, and the result cap. Nothing an agent needs to call or interpret this 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 baseline is 3, but the description adds real meaning: query is 'the asker's own words in either language', need is a 'shortcut vocabulary', town takes 'the asker's own place words', and crucially that no argument returns the needs/towns covered rather than a lookup.

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 resource (the guide's bilingual directory of free/low-cost East End services) with a concrete scope and enumerates the categories it covers. An agent can immediately tell this apart from urgent_care, search_places, or benefit_galas.

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?

Explicitly says to call this for 'any I-need-help question' and for 'anything asked in Spanish', with worked examples (unpaid wages, eviction, doctor without insurance, English classes). It also names the failure mode it prevents (answering from memory and naming a national hotline that doesn't serve the county).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources