Skip to main content
Glama

AgentSynta Business Beacon

List businesses

list_businesses
Read-onlyIdempotent

List published AgentSynta businesses, optionally filtered by name, industry or city.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_businesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25).
queryNoFilter by name, industry or city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description adds one genuinely useful behavioral fact — only published businesses are returned — but says nothing about result ordering or what happens when limit is hit beyond what the schema states.

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?

A single front-loaded sentence with the resource, scope and filter dimensions in order of importance. No filler, no repetition of name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only list tool with full schema coverage and no output schema, the definition covers what an agent needs: what is listed, the published-only scope and the filter dimensions. Only very minor gaps remain (ordering, result shape), which the annotations and schema largely absorb.

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%, so both parameters are already documented in the schema, and the description merely restates that the filter covers name, industry or city. It adds no matching semantics (exact vs substring) beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List ... businesses") plus a meaningful scope qualifier ("published") and the filterable fields. It is clearly distinguishable from the sibling get_/search_ tools, though it does not explicitly name an alternative, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Optionally filtered by" implies the tool can be used with or without filters, which is useful usage framing, but there is no explicit when-to-use guidance, no statement of when to prefer search_offerings-style tools, and no mention of prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources