Skip to main content
Glama
sinhasulabh

Meridian Commercial Intelligence MCP Server

by sinhasulabh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_segment_attainmentA

Q1 2026 closed-won attainment vs. quota for one segment.

Args:
    segment: One of "Enterprise", "Mid-Market", "SMB".
    viewer: "LEADERSHIP" or a rep_id (e.g. "REP-02"). Required.
get_reps_at_riskA

Reps whose Q1 2026 closed-won attainment is below threshold.

Args:
    viewer: "LEADERSHIP" or a rep_id. Required.
    threshold: Attainment cutoff in [0.0, 1.0]. Defaults to 0.70.
get_pipeline_valueA

Sum of open-stage deal_value, optionally filtered.

Args:
    viewer: "LEADERSHIP" or a rep_id. Required.
    segment: Optional segment filter.
    close_before: Optional ISO date; keeps deals with close_date <= this.
get_deal_reasonA

The stored loss_reason for one account, verbatim. Refuses if empty.

Args:
    account_name: The account to look up.
    viewer: "LEADERSHIP" or a rep_id. Required.
list_supported_questionsB

The governed capability set — what this system can and can't answer.

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.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool addresses a distinct commercial intelligence query: segment attainment, at-risk reps, pipeline value, deal loss reason, and capability listing. There is no overlap in purpose, making selection unambiguous.

Naming Consistency4/5

The majority of tools follow a 'get_' + object pattern (get_segment_attainment, get_reps_at_risk, get_pipeline_value, get_deal_reason), but 'list_supported_questions' deviates by using 'list_' instead. Minor inconsistency, otherwise predictable.

Tool Count5/5

Five tools is well-scoped for a commercial intelligence server. Each tool covers a distinct capability without bloat, and the count is appropriate for the domain.

Completeness4/5

The coverage includes key metrics (attainment, risk, pipeline, loss reasons) and a self-describing capability list. However, some common queries like win rate or quota details are absent, presenting minor gaps that agents may need to work around.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources