centric-demo
Server Details
Try Centric relationship intelligence: Brief Me, Relational IP radar, Draft As. Demo data.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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
Average 4/5 across 6 of 6 tools scored. Lowest: 3.2/5.
Each tool has a distinct purpose: brief_me provides a synthesis, demo_temperature_check walks through an interaction, draft_as drafts in formats, get_contact_profile gives full profile, get_radar gives radar shape, and list_demo_contacts lists contacts. There is no overlap or ambiguity.
Five tools follow verb_noun pattern (brief_me, draft_as, get_contact_profile, get_radar, list_demo_contacts). One tool (demo_temperature_check) deviates by using a compound noun prefix, breaking the pattern slightly.
With 6 tools, the set is well-scoped for a demo server covering key features: listing, profiling, radar, briefing, drafting, and a step-through interaction. Each tool earns its place without being excessive or too few.
For its stated domain of demo contact management, the tool set covers essential read operations (list, profile, radar), a synthesis (brief), a draft action, and an interaction walkthrough. No obvious gaps exist, as write operations are intentionally omitted for demo purposes.
Available Tools
6 toolsbrief_meInspect
The Brief Me hero tool. Returns a synthesized pre-interaction brief for a demo contact — personality read, what to open with, what to avoid — plus a cadence heads-up when the relationship is in a Watch state.
| Name | Required | Description | Default |
|---|---|---|---|
| contact | Yes | Contact id or name, e.g. 'Isabella Chen' |
demo_temperature_checkInspect
Walk through the temperature check interaction for a demo contact: shows the prompt and the Positive / Neutral / Concern options, and returns a canned acknowledgment. Demonstrates the loop without saving anything.
| Name | Required | Description | Default |
|---|---|---|---|
| read | No | Optional: the read to simulate. Omit to just see the prompt. | |
| contact | Yes | Contact id or name, e.g. 'Isabella Chen' |
draft_asInspect
Draft outreach to a demo contact in a chosen format: email, text, linkedin, or talking_points. Demonstrates Centric's Draft As feature — the draft is grounded in the contact's brief context. Demo only; nothing is sent or logged.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Draft format. Defaults to email. | |
| contact | Yes | Contact id or name, e.g. 'Isabella Chen' |
get_contact_profileInspect
Get the full RM-facing profile for one demo contact: the five Relational IP dimensions as Red/Yellow/Green, a Brief Me summary, cadence note, and current context. No numeric score — RMs see status, not the number.
| Name | Required | Description | Default |
|---|---|---|---|
| contact | Yes | Contact id or name, e.g. 'Isabella Chen' |
get_radarInspect
Get the Relational IP radar shape for a demo contact: five axes, each a Red/Yellow/Green status plus a normalized 0–1 position for rendering the widget. Intentionally returns no numeric score.
| Name | Required | Description | Default |
|---|---|---|---|
| contact | Yes | Contact id or name, e.g. 'Isabella Chen' |
list_demo_contactsInspect
List the demo book of business — the fictional contacts Centric is tracking for demo RM Marcus Johnson. Returns name, title, company, R/Y/G health, and days since last touch. Start here.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
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!