Skip to main content
Glama

Lokand Restaurant MCP

Claim status

claim_status
Read-onlyIdempotent

Check whether the customer has claimed an agent-created restaurant. On the first poll after a claim with consent granted, returns fresh OAuth tokens for continued management (delivered exactly once).

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": {
      "client_id": "<client_id>",
      "client_secret": "<client_secret>",
      "claim_token": "<claim_token>"
    },
    "name": "claim_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYesRegistered OAuth client id
claim_tokenYes
client_secretYesThe client's secret

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?

Beyond the annotations (readOnly, non-destructive, idempotent, open-world), the description discloses two things the structured fields cannot: that successful polling yields fresh OAuth tokens for continued management, and that those tokens are delivered exactly once, so a missed first poll cannot be recovered. That exactly-once detail is critical for the caller to persist the response. It stops short of describing the possible status values returned when no tokens are issued.

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 tightly written sentences with no filler. The core purpose is front-loaded, and the non-obvious exactly-once token behavior follows immediately as the second point of emphasis.

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 simple three-parameter polling endpoint with no output schema, the description covers the essential purpose plus the one behavior an agent could not guess: one-time OAuth token delivery. It leaves the response shape and the pending-versus-claimed status values implicit, which is a modest but real gap for a tool whose whole job is reporting status.

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 coverage is 67%; client_id and client_secret are documented in the schema, but claim_token has no description of its own. The description provides only indirect context for the token ('after a claim with consent granted') and says nothing about where the claim_token originates or how the client credentials relate to it, so it neither compensates for the gap nor adds meaning beyond the 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?

States a specific verb and resource: check whether the customer has claimed an agent-created restaurant. That is far more precise than the title alone. It does not differentiate itself from status-oriented siblings such as get_status or import_status, so an agent must infer the distinction from the name.

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?

The phrase 'On the first poll after a claim' implies this is a polling tool used in the post-claim flow, which is useful implied guidance. However, it never says when to use this rather than get_status, how frequently to poll, or what to do if the claim is still pending, so the agent must infer the workflow.

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