Skip to main content
Glama
siffletdata

sifflet-mcp

Official
by siffletdata
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SIFFLET_API_TOKENYesAPI token for Sifflet. A token with Viewer role is enough for most tools. The get_monitor_code_by_description tool additionally requires Editor role on the targeted domain.
SIFFLET_BACKEND_URLYesFull URL to the Sifflet backend, e.g. https://<tenant_name>.siffletdata.com/api/

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
asset_by_urnA
    Get asset information by urn. The urn is the unique identifier a asset, for example dataset:0826ce5c-7027-4857-aa47-b639265d1867. It can be found when you search for an asset.
search_assetA
    Search assets, tables, dashboards, pipelines.
    asset_type can be one of the following: TABLE_AND_VIEW, PIPELINE, DASHBOARD, ML_MODEL
    health_status can be one of the following: URGENT_INCIDENTS, HIGH_RISK_INCIDENTS, NO_INCIDENTS, NOT_MONITORED, UNSUPPORTED
    owners is a list of owners emails associated with the asset
    tags is a list of tags associated with the asset
    text_search is a string to search in the asset name or description
    items_per_page is the number of items to return per page
    page is the page number to return. Pages start at 0.
search_incidentsA
      Search incidents
      Sort is done by createdAt by default. By default sort is descending. But you can change it using sort=asc.
      You can filter by status, user and text search.
      Status can be OPEN, IN_PROGRESS, CLOSED.
      Text search is a string.
      Pages start at 0.
get_incident_by_issue_numberA

Get incident details by issue number. The issue number is the unique identifier of the incident, for example 1234.

get_incident_scope_by_issue_numberA

Get incident scope by issue number. The issue number is the unique identifier of the incident, for example 1234. The scope is the list of assets and monitors associated with the incident.

get_monitor_details_by_idA
    Get monitor details by id. 
    The monitor_id is the monitor UUID. The id can be found when you search for a monitor.
    monitor_id is the unique identifier of the monitor, for example 3b8a1333-aef0-468a-893b-e87dfc095c82
close_incident_by_idA
    Close an incident by id. The id is the unique identifier of the incident, for example 1234.
    The should_qualify_monitor is a boolean that indicates if the monitor should be qualified or not.
open_incident_by_idB

Open an incident by id. The id is the unique identifier of the incident, for example 1234.

get_monitor_code_by_descriptionA
    Returns a monitor configuration based on the input query
    The input is a description of the monitor you want to create.
    The description should be a natural language description of the monitor you want to create.
    The dataset_ids is a list of dataset ids that the monitor should be applied to. You must provide at least one dataset id. You can find the id of the dataset using search_asset. 
    The description is a string that describes the monitor you want to create. For example: "Create a monitor that checks if the number of rows in the table is greater than 1000".
    The result is a YAML string that contains the monitor configuration.
get_downstream_assets_of_assetA
      Get all downstream assets of an asset. An Urn is the unique identifier of an asset, for example dataset:0826ce5c-7027-4857-aa47-b639265d1867. It can be found when you search for an asset.

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

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct purposes (asset lookup vs incident search vs monitor details). However, incident tools use different identifiers ('by_id' vs 'by_issue_number') for what appears to be the same entity, which could confuse an agent. Asset tools by URN are distinct but share similar input patterns.

Naming Consistency3/5

Naming conventions are mixed: 'asset_by_urn' does not follow the verb-first pattern used by most others, and pluralization is inconsistent ('search_asset' vs 'search_incidents'). Incident tools also inconsistently use 'by_id' versus 'by_issue_number'.

Tool Count5/5

10 tools is well-scoped for a data observability platform, covering assets, monitors, and incidents without being overwhelming. Each tool serves a distinct function, and the count fits comfortably within the ideal range.

Completeness3/5

Core workflows like asset search/detail, incident management, and monitor code generation are covered. However, there is no tool to search or list monitors (only get by ID), no monitor creation/update, and only downstream asset lineage (no upstream). These are notable gaps for a monitoring-focused tool.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources