Find a food pantry near a US location (ZIP or City, ST) from ~17,000 pantries. Free.
Find nearby food pantries for someone who needs food. Give a location — a US ZIP code, "City, ST", or "lat,lng" — and it returns the closest pantries with address, phone, website and distance, from a directory of ~17,000 US food pantries. Use it when someone asks where to get free food or find a food pantry. Free, no signup. Call the pantry to confirm hours and eligibility before visiting — this tool does not have live hours.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many pantries to return (default 5, max 15). | |
| location | Yes | US ZIP code, "City, ST", or "lat,lng". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish this as read-only, idempotent, and non-destructive. The description goes beyond this safety profile by disclosing the ~17,000-entry dataset, the absence of live hours, the instruction to call the pantry, and that it is free with no signup. This is useful context, though it does not address potential errors or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences front-load the purpose, then compactly cover input formats, output details, usage context, and the live-hours caveat. There is no filler and every sentence contributes to helping the agent decide and invoke the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description compensates by listing return fields (address, phone, website, distance) and input formats, plus the data source size and a key limitation. For a two-parameter tool with full schema coverage and no siblings, nothing essential is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with both 'location' and 'limit' documented including examples, defaults, and max. The description repeats the location formats but adds little beyond what the schema already provides, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with 'Find nearby food pantries' and enumerates exactly what the tool returns: closest pantries with address, phone, website, and distance. Even with no siblings, the verb+resource+scope is specific and distinguishes the tool's directory of ~17,000 US food pantries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly states 'Use it when someone asks where to get free food or find a food pantry', which is clear use-case guidance. There are no sibling tools or alternatives, so exclusions are not needed; the absence of a 'when not to use' is not a meaningful gap here.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
find_food_pantryClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Search foods, compare nutrients, and look up the full USDA FoodData Central database.
Find free stuff near any US ZIP, priced for resale. Live listings, resale estimates, alerts.
Cached US grocery prices, age disclosed on every row - search, compare across banners, coverage.
Barcode lookup, nutrition search, and product comparison for 3M+ crowd-sourced food products.
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of confusing it with another. The tool's purpose is entirely clear and unambiguous.
The single tool uses a clear verb_noun pattern (find_food_pantry), and with no other tools there are no mixed conventions.
One tool is slightly below the typical 3-15 range, but it directly serves the server's narrow purpose of locating food pantries, so the count is still reasonable.
The tool fully addresses the stated domain of finding nearby food pantries by returning address, phone, website, and distance. The lack of live hours is transparently noted rather than a missing operation.
