53ON

search_providers

Read-only

Find 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.

Input Schema

TableJSON Schema

Name	Required	Description
`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.

TDQS

A4.7/5.0

Behavior5/5

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.

Conciseness5/5

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.

Completeness5/5

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.

Parameters4/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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.

All 53ON tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness3/5

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.

Resources

Need Help?