Skip to main content
Glama

Lokand Restaurant MCP

Get billing summary

get_billing_summary
Read-onlyIdempotent

Current plan, billing region, and subscription state of a business the caller manages.

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_billing_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful qualifier that the business must be one the caller manages, implying an authorization check and possible failure mode, but says nothing about error behavior or what is returned when billing is unconfigured.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence, front-loaded with the returned fields and with zero filler. It loses a point only because the fragment construction omits the action verb that would make it self-contained.

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 single-parameter read-only tool with no output schema, enumerating the returned fields plus the caller-manages scoping covers most of what an agent needs to invoke it. The remaining gap is the identifier format and the failure behavior for inaccessible businesses.

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?

One required parameter with 0% schema description coverage, so the schema only gives type and minLength. The phrase 'a business the caller manages' implicitly characterizes business_id as a manageable-business identifier, adding some meaning, but format (ID vs. slug) and sourcing (list_businesses) remain unstated.

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

Purpose3/5

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

The description enumerates the data returned (plan, billing region, subscription state), which distinguishes it from the many business/storefront siblings, but it is a bare noun phrase with no verb — an agent must infer 'retrieve'. It names the resource clearly enough to select it, yet never states the action.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as get_business or get_status, which plausibly overlap with business-level data retrieval. The only usage constraint implied is 'a business the caller manages', which is a permission condition, not a routing rule.

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