Skip to main content
Glama
Sign In
MGC_MCP

MGC_MCP

by maskelog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check Mega MGC Coffee stock nationwide or by region

check_mgc_stock_nationwide

Check stock availability (sold-out status) of Mega MGC Coffee menu items nationwide. Filter by region or item code to find stores with available items.

Instructions

Check Mega MGC Coffee app API sold_out values across stores nationwide or filtered by region. Use itemCode for exact lookup when known.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_mgc_stock_nationwide"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity/province token, for example 서울 or 대구.
districtNoDistrict token, for example 종로구.
itemCodeNoMega MGC app item_cd. Example: 107350.
maxStoresNoMaximum stores to check.
concurrencyNoConcurrent app API requests.
productNameNoMenu/product name, for example 와앙 핫 치즈스틱 & 딥.
regionQueryNoFree-form region query. Example: 서울 종로구 or 서울 종로구 이화동 혜화동. First two tokens are city/district, remaining tokens are neighborhoods matched as OR.
resultLimitNoMaximum stores returned per result group.
neighborhoodsNoNeighborhood tokens matched as OR after city/district, for example ["이화동", "혜화동"].
refreshStoresNoForce refresh store cache before stock check.
regionKeywordNoRegion keyword where all whitespace-separated tokens must match store name/address.
regionKeywordsNoAlternative region phrases. A store matches if any phrase matches all its tokens.
storeCachePathNoCache file path. Default: data/mgc-stores.json.
storeCacheTtlHoursNoCache TTL in hours.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only mentions 'sold_out values' and 'app API' but does not disclose caching behavior, concurrency limits, read-only nature, or potential side effects. Key behavioral traits are omitted.

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?

Two sentences, no fluff, front-loaded with main function. Could be improved by structuring hints into a list, but overall efficient and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 parameters and no output schema, description fails to explain return format or how to interpret results. Also does not clarify when this tool is preferred over sibling tools like check_mgc_stock_by_region. Information is incomplete for an AI to use confidently.

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 description coverage is 100%, so baseline is 3. Description adds minimal extra meaning beyond schema for itemCode, but does not enhance understanding of other parameters like regionQuery or cache options. No significant added value.

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?

Description uses specific verb 'Check' and resource 'Mega MGC Coffee app API sold_out values across stores' and distinguishes from siblings by mentioning nationwide or region filter. It also hints at exact itemCode lookup, making purpose clear.

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?

Gives one hint ('Use itemCode for exact lookup when known') but does not explicitly state when to use this tool vs siblings like check_mgc_stock_by_region or find_mgc_stores. Implies general usage but lacks exclusion criteria.

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