Directory and marketplace of local businesses and independent professionals. Find who does a job near a user, see ratings and prices, and get a direct link to request a quote and pay. Two tools: search_providers finds businesses by what they do (Spanish or English, resolves synonyms, optional lat and lng) and get_business returns one business detail: services, ratings, product catalog with prices, and the quote-and-pay link. Stateless streamable-http, no auth.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Average 4.2/5 across 2 of 2 tools scored.
The two tools have completely distinct purposes: search_providers finds businesses based on query and location, while get_business retrieves detailed information for a specific business by slug. No ambiguity exists between them.
Both tools follow a consistent verb_noun snake_case pattern (get_business, search_providers). The naming is predictable and matches the operations they perform.
With only two tools, the surface is thin but still coherent for a focused read-only business directory. It covers search and detail retrieval, but the narrow scope makes it borderline appropriate.
The tool set covers the core workflow of finding a business and viewing its details, including the link for quotes/payment. Missing operations like user-specific actions or list-all functionality are minor gaps given the public directory purpose.
get_businessAInspectFull public detail of one 53ON business by its slug: services, ratings, product catalog with prices, and the link where the user can request a quote and pay. Use the slug returned by search_providers.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Language for service names. Default es. | |
| slug | Yes | Public slug of the business, for example creacionlaura. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It indicates the tool is read-only in nature ('public detail', 'link where user can request a quote and pay'), implying no side effects. But it doesn't detail edge cases like missing slug or rate limits. It's adequate but minimal.
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?
Two sentences, front-loaded with the core purpose, then a practical usage hint. No wasted words.
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?
For a simple 2-parameter read tool with high schema coverage, the description covers the key behavior and usage. It lacks details about error handling or return structure, but given no output schema and simple parameters, it's largely complete.
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?
The input schema has 100% coverage, with descriptions for both parameters. The description adds context about the source of slug (from search_providers) and that lang defaults to es. Since schema covers everything, a 3 is appropriate.
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 clearly states the tool's purpose: fetching full public detail of one business by slug, listing specific content (services, ratings, product catalog with prices, quote/payment link). It also distinguishes from sibling tool by referencing the slug returned by search_providers.
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 instructs to use the slug from search_providers, indicating when to use this tool (after searching). It doesn't specify when not to use it, but the context is clear. Provides a usage prerequisite.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_providersAInspectFind local businesses and independent professionals on 53ON by what they do. Accepts free text in Spanish or English and resolves synonyms, so "plumber" and "destapar caneria" both work. Pass lat and lng to limit results to that area; without them the search is nationwide. Call with an empty query to get the list of services 53ON covers.
| Name | Required | Description | Default |
|---|---|---|---|
| lat | No | Latitude of the user. Optional. | |
| lng | No | Longitude of the user. Optional. | |
| lang | No | Language of the query. Default es. | |
| limit | No | Max results, 1 to 50. Default 10. | |
| query | No | What the user needs, in their own words. Empty returns the service list. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses key behaviors: bilingual support, synonym resolution, location-based scoping, and empty-query behavior. It does not mention potential side effects or permissions, but as a search tool it is likely read-only. The description gives good proactive transparency.
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, each packed with useful information. No filler. Front-loaded with the core purpose, then additional behaviors. Very concise and well-structured.
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?
Given 5 parameters, no output schema, and no annotations, the description covers the main usage patterns: search by query, optional location, language support, and empty query special case. It does not describe result format or ordering, but for a search tool this may be acceptable. The level of detail is appropriate for the tool's complexity.
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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema: it explains lat/lng control area scope, and that empty query returns service list (for query param). It does not add details for lang or limit, but the schema already covers those. The added context elevates it above baseline.
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 clearly states the tool's purpose: finding local businesses and professionals by what they do. It specifies the resource (53ON), the verb (Find), and the scope (by what they do). The sibling tool get_business is implicitly different (fetching a specific business vs. searching), and the description provides enough distinction.
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?
The description explains when to use the tool: to search by service/type, with optional location constraints. It explicitly states that omitting lat/lng yields nationwide results and that an empty query returns the service list. However, it does not explicitly contrast with get_business or state when NOT to use this tool, though the context makes that reasonably clear.
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.
No comments yet. Be the first to start the discussion!
