Skip to main content
Glama
msoutumuro123

Restaurant365 MCP Server

by msoutumuro123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
r365_test_connectionA

Verify live connection to Restaurant365 OData using configured credentials. Returns location count on success.

r365_list_entitiesB

List all available Restaurant365 OData entity endpoints.

r365_list_locationsC

Retrieve all Restaurant365 locations accessible to the configured user.

r365_queryA

Run a read-only OData query against any R365 entity.

Args:

  • entity: OData view name (Location, Transaction, GlAccount, etc.)

  • filter: OData $filter expression (e.g. "date ge 2026-01-01T00:00:00Z")

  • select: OData $select comma-separated fields

  • orderby: OData $orderby expression

  • top: Max rows (default 100, max 1000)

  • skip: Offset for pagination

r365_get_transactionsA

Retrieve financial transactions from Restaurant365.

Args:

  • location_id: Optional location GUID filter

  • date: Optional business date filter (ISO 8601, e.g. 2026-06-01T00:00:00Z)

  • type: Optional transaction type (e.g. 'Journal Entry', 'AP Invoice')

  • top: Max rows (default 100)

r365_get_gl_accounts

Retrieve GL account master data from Restaurant365.

r365_get_employees

Retrieve employee records from Restaurant365.

r365_get_sales

Retrieve sales ticket headers from Restaurant365 SalesEmployee view.

Args:

  • location_id: Optional location GUID

  • date: Optional business date (ISO 8601)

  • top: Max rows (default 100)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool serves a distinct purpose: connection verification, entity enumeration, location listing, generic querying, and transaction retrieval. No overlap or ambiguity.

Naming Consistency5/5

All tools follow the 'r365_' prefix and snake_case naming convention. Most use verb_noun pattern (test_connection, list_entities, list_locations, get_transactions), with 'r365_query' being a concise verb form, maintaining overall consistency.

Tool Count5/5

Five tools is appropriate for a read-only OData API server, covering connection testing, schema discovery, location listing, generic querying, and a specific transaction query without being excessive or sparse.

Completeness4/5

The set provides essential read-only operations: test, list entities, list locations, generic query, and specific transaction query. While a dedicated get-by-ID tool is missing, the generic query can handle it via filters. No write operations are expected per scope.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources