Directory and marketplace of local businesses and independent professionals near you.
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.6/5 across 2 of 2 tools scored.
The two tools have completely distinct purposes: one retrieves a single business's details, the other searches for businesses. There is no ambiguity between them, and the descriptions clearly indicate when to use each.
Both tool names follow the same verb_noun pattern: get_business and search_providers. The naming is consistent and predictable, making it easy for an agent to infer their behavior.
With only two tools, the server feels thin but not entirely unreasonable for a focused lookup service. However, the scope of the domain (finding local businesses) might warrant additional tools for browsing or filtering, making the count borderline.
The tool set covers the core workflow of searching for a provider and fetching its details, but it lacks broader browsing capabilities, such as listing all businesses in an area or filtering by service category directly. This is a notable gap but not a fatal one for basic use cases.
get_businessAFull 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?
Annotations declare readOnlyHint=true and openWorldHint=true, and the description reinforces that this is a public, read-only lookup by saying 'Full public detail.' It also adds meaningful context about what the response includes, including the quote/payment link, which goes beyond the annotation metadata.
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?
The description is a single, front-loaded sentence that immediately states the tool's purpose and key delivery. Every phrase earns its place: scope ('one business'), identifier ('by its slug'), content summary, and the source of the slug.
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 two-parameter read-only lookup with no output schema, the description is sufficiently complete. It explains what the caller gets, how to obtain the required identifier, and the public nature of the operation, so an agent can invoke it confidently.
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%, with both slug and lang already described. The description adds extra meaning by tying the slug directly to the output of search_providers and clarifying it identifies one specific business. It does not add much for lang, but the schema already covers that adequately.
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 that this tool fetches full public details for exactly one business by slug, and enumerates the key content areas (services, ratings, product catalog with prices, quote/payment link). It also distinguishes itself from the sibling search_providers by specifying that the slug comes from that search tool.
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 gives clear usage context: use the slug returned by search_providers, which implies this is the follow-up detail lookup after searching. It does not explicitly state when not to use this tool, but the connection to search_providers provides sufficient orientation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
search_providersAFind 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?
Beyond the readOnly/openWorld annotations, the description discloses synonym resolution, language support, geographic fallback behavior, and the empty-query special case. This gives the agent important behavioral expectations without contradicting the annotations.
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?
The description is compact and front-loaded with the core purpose, and every sentence earns its place by covering a distinct behavior or usage case. No redundant filler.
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 the tool's moderate complexity and full schema documentation, the description provides enough behavioral and contextual detail for reliable selection and invocation, including language, geographic filtering, and empty-query behavior.
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 schema already covers all parameters at 100%. The description adds useful semantics beyond the schema: lat/lng scoping behavior, nationwide default, and empty query meaning. It does not add much on lang/limit, but the schema covers those clearly.
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 a specific verb and resource: 'Find local businesses and independent professionals on 53ON by what they do.' It clearly defines search scope (by activity), differentiates from the sibling get_business, and illustrates behavior with synonyms.
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 gives clear context: free text, Spanish/English, optional lat/lng for area limiting, nationwide without, and empty query for service list. It does not explicitly mention when to prefer get_business instead, so it misses an explicit exclusion or alternative comparison.
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!