Skip to main content
Glama

Lokand Restaurant MCP

List businesses

list_businesses
Read-onlyIdempotent

List the businesses the signed-in user is a member of (id, name, slug, role). Use it to pick the business_id other ops need.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds real value beyond them: results are filtered to the caller's memberships, and with no output schema it enumerates the returned fields, so the agent knows the shape of the response. Auth is only implied by 'signed-in user', and nothing is said about behavior when the user belongs to no businesses.

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 short clauses: scope and returned fields first, then the practical usage cue. Nothing is repeated from the annotations or schema, and no sentence is wasted.

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 parameterless, read-only list operation with no output schema, the description covers what is returned and why an agent would call it. Minor gaps remain around auth requirements and the empty-list case, but nothing needed to invoke it correctly is missing.

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 tool takes zero parameters, which is the baseline-4 case. The parenthetical field list describes output rather than inputs, so it does not conflict with the empty schema.

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?

The description states a specific verb and resource ('List the businesses') plus the scope restriction ('the signed-in user is a member of') and names the returned fields (id, name, slug, role). It reads clearly against a 'get_business' style sibling by being explicitly plural and caller-scoped, though it does not name that sibling outright.

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?

'Use it to pick the business_id other ops need' gives a concrete selection context: it is a discovery/entry-point call whose output feeds other tools. It does not state exclusions (e.g., when to use a single-business lookup instead), but for a zero-parameter enumeration tool the positive guidance is sufficient to route an agent.

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