MCP CPG Agent Protocols
Server Details
BPC Agentic Commerce Signals
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- greencore-solutions/cpg-agent-protocols
- GitHub Stars
- 0
- Server Listing
- MCP CPG Agent Protocols
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
9 toolsget_header_canonGet the Ghost Headers canonInspect
The GSC wire-header canon (v3.2 — The Ghost Eighteen (locked July 18 2026)) — the eighteen x-gsc-* headers every GSC surface emits, in canon order. Curl-auditable against any live GSC surface.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_protocolGet one protocolInspect
Full canon record for ACM-SPARKS, SM-ECO-10060, or ACM-68000.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Protocol name |
list_membersList SM-ECO-10060 membersInspect
The 49 sovereign jurisdictional member nodes — code, namespace, jurisdiction, region, and GS1 territory GTIN. Live supply/demand data per member is the CPG Knowledge Graph's job.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_protocolsList the three GSC protocolsInspect
The protocol family and the resolve-once spine: ACM-SPARKS classifies, SM-ECO-10060 resolves, ACM-68000 signals.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_signalsList the 7 ACM-68000 signalsInspect
All seven signals, enumerated individually: ACM-000, ACM-200, ACM-300, ACM-403, ACM-404, ACM-451, ACM-500. One meaning, no drift.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_sparks_dimensionsList the six SPARKS dimensionsInspect
SPARKS resolves six dimensions — SKU, Pack, Amount, Region, Kernel, and Standard — a CPG industry first.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
resolve_memberResolve one SM-ECO-10060 memberInspect
Canon record for a single sovereign member by ISO-style code, e.g. FR, AU, MX.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Member code, e.g. FR |
resolve_signalResolve one signal codeCInspect
The state and meaning of a single ACM-68000 signal code.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Signal code, e.g. ACM-451 |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as side effects, idempotency, or authentication needs. It only states the return concept without behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is only one sentence, which is concise, but it is too brief to fully inform an agent. It could include more detail without being verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (1 param, no output schema), the description is minimal. It lacks explanation of what 'state and meaning' entails, and no example or return format, making it incomplete for confident use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for the single parameter 'code', and the description adds minimal meaning beyond the schema (stating 'state and meaning'). Baseline 3 is appropriate as the parameter is well-documented in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states it resolves a single ACM-68000 signal code to its state and meaning, clearly specifying the tool's purpose and resource. It distinguishes from siblings like list_signals which list all signals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like list_signals or resolve_member. No prerequisites or context provided for appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
resolve_sparks_dimensionResolve one SPARKS dimensionInspect
Canon record for a single SPARKS dimension by letter (S, P, A, R, K, S2) or name.
| Name | Required | Description | Default |
|---|---|---|---|
| dimension | Yes | Letter (S, P, A, R, K, S2) or name (e.g. Pack-format) |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.