Skip to main content
Glama
Sign In
gingr-mcp

gingr-mcp

by shashicandev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get an owner's reservations

gingr_get_owner_reservations
Read-only

Retrieve all reservations for a specific owner to analyze customer history, visit frequency, and lifetime value.

Instructions

Get all reservations for a specific owner (customer). Use to analyze a customer's history, frequency, and lifetime value. Get owner_id from gingr_list_owners first.

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": {
      "owner_id": "<owner_id>"
    },
    "name": "gingr_get_owner_reservations"
  }
}

Input Schema

NameRequiredDescriptionDefault
owner_idYesGingr owner/customer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true; the description adds that it returns all reservations for an owner, which is sufficient behavioral context for a simple read tool. No contradictions.

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 sentences: first states purpose and use case, second provides prerequisite. No filler words, front-loaded with key info.

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?

Given simple tool with one parameter and no output schema, the description adequately explains the return value (reservations) and use case, sufficient for complex evaluation.

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 covers 100% of parameters with description of owner_id. The description adds no further param details beyond usage hint, meeting baseline for high coverage.

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

Purpose5/5

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

The description clearly states the verb 'Get all reservations' and the resource 'for a specific owner', and it distinguishes from siblings like gingr_list_reservations by specifying owner filter.

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?

The description advises using the tool to analyze customer history and explicitly tells to get owner_id from gingr_list_owners first, providing clear prerequisite guidance. No explicit when-not-to-use, but context is adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools