A
licenseA
qualityD
maintenanceWheelchair accessibility data for 105,000+ locations across 15 US states. Enables search, details, and feedback submission through natural language.
5
48
1
MIT
Persnickety Try-On Index
Server Details
Find source-checked US boutiques with plus-size bridal samples physically available to try on.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.1/5.0
Tool DescriptionsA
Average 4.3/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of ambiguity. The tool's purpose is clearly stated.
Naming Consistency5/5
The single tool name follows a clear verb_noun pattern (find_bridal_samples), establishing a consistent naming style.
Tool Count3/5
With only one tool for a server named 'Persnickety Try-On Index', the surface feels thin for an index-based service, but it may be acceptable for a very focused task.
Completeness2/5
The server lacks tools for browsing boutiques, checking real-time availability, or managing appointments, leaving obvious gaps for a try-on index service.
Available Tools
1 toolfind_bridal_samplesFind Plus-Size Bridal SamplesARead-onlyIdempotentInspect
Find source-checked US bridal boutiques where a requested plus-size wedding dress sample is published as physically available to try on. Results are not real-time; confirm before traveling.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Boutique, city, or state search text | |
| size | No | US bridal sample size | |
| state | No | Two-letter US state code |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| data | Yes | |
| meta | Yes |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate read-only, idempotent behavior. Description adds crucial behavioral context: results are source-checked but not real-time, and physical availability is emphasized. This goes beyond the annotations and helps the agent set proper expectations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences: first defines the core action, second provides an important caveat. No redundancy or irrelevant information. The description is well front-loaded and earns each sentence.
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?
Given the tool's simplicity (three optional params, output schema exists, annotations rich), the description covers all essential aspects: what it finds, source-checking, non-real-time nature, and physical availability. No gaps remain for agent decision-making.
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% (all three parameters have descriptions in the input schema). The description adds limited extra meaning—tying 'plus-size' to the size parameter and 'US' to state—but does not significantly enhance what the schema already provides. Baseline of 3 is appropriate.
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?
Description clearly states the tool finds US bridal boutiques with physically available plus-size wedding dress samples. Verb 'find' and specific resource are explicit, and the non-real-time caveat adds clarity. No sibling tools exist to differentiate, but the purpose is precise.
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?
Description provides clear context: use to locate source-checked boutiques with available samples. The non-real-time warning and suggestion to confirm before traveling serve as usage guidance. No exclusions or alternatives are needed due to lack of siblings, but the guidance is helpful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceEnables searching and comparing GLP-1 medication providers, medications, side effects, and FAQs across a directory of 18,344 US clinics, telehealth programs, and pharmacies.39MIT
- Alicense-qualityDmaintenanceQuery 13,000+ US consumer lenders with eligibility criteria, rates, CFPB complaints, and ratings. Find matching lenders by borrower profile, get full profiles, compare lenders, and check eligibility.MIT
- AlicenseAqualityBmaintenanceFind 76,000+ curated healthcare service vendors across 25 categories and all 50 US states. Search by category, specialty, city, state, and EHR system to identify billing, credentialing, EHR, and practice-consulting vendors that serve medical practices.3MIT