Skip to main content
Glama

Lokand Restaurant MCP

Get status

get_status
Read-onlyIdempotent

Private status of a business the caller manages: profile (including unpublished state), all menus (active and inactive), and plan. Requires the menu:read scope and membership.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "business_id": "<business_id>"
    },
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYesThe business id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: the payload is private data, it deliberately includes unpublished profile state and inactive menus, and it requires the menu:read scope plus membership. The auth/permission requirement in particular is not derivable from annotations or schema.

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 tight sentences: the first front-loads what the tool returns with parenthetical qualifiers, the second states the access prerequisite. No preamble, no redundancy, nothing that could be cut without losing information.

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 one-parameter read tool with no output schema, the description usefully enumerates the response contents (profile, menus, plan) and the permission requirements, which is what an agent needs before calling. Minor gap: it doesn't state whether results are paginated or bounded, though for a status overview that is a low-stakes omission.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents business_id. The description adds no further detail about the id's format or where to obtain it. Baseline 3 applies when the schema carries the parameter burden.

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 names a specific resource ('private status of a business') and enumerates exactly what is returned: profile including unpublished state, all menus active and inactive, and plan. That's far more informative than the tautological title. It stops short of explicitly distinguishing itself from siblings like get_business or get_menu, which likely overlap on profile/menu data.

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?

Usage is implied rather than stated: 'private status of a business the caller manages' signals this is the management-side overview rather than a public/storefront read, and the enumeration of contents implies when it is the right call. However, no sibling is named and there is no explicit when-not-to-use guidance against get_business, get_menu, or get_billing_summary.

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