Skip to main content
Glama
sanyambassi

thales-cdsp-csm-mcp-server

by sanyambassi

manage_analytics

Retrieve comprehensive infrastructure monitoring and usage analytics, including security risk analysis and certificate expiry tracking, for compliance reporting and capacity planning.

Instructions

ANALYTICS & MONITORING TOOL - Comprehensive infrastructure monitoring and reporting

SUPPORTED ACTIONS: • get: Retrieve comprehensive monitoring data, usage statistics, and performance metrics

ANALYTICS COVERAGE: • Usage statistics and item counts by type (Secrets, Targets, Roles, Keys) • Geographic distribution of access requests and client patterns • Security risk analysis and certificate expiry tracking • Authentication method usage and access control compliance • Multi-region usage distribution and product-specific metrics • Resource utilization, capacity planning, and audit summaries

FILTERING OPTIONS: • Filter by item type (Targets, Static Secrets, Dynamic Secrets, DFC Keys, etc.) • Filter by risk level (Expired, Healthy, Expiring Soon certificates) • Filter by product component (Secrets Management, Advanced Data Protection, etc.)

USE CASES: • Security operations center (SOC) dashboards • Compliance reporting and audit preparation • Capacity planning and resource optimization • Risk assessment and vulnerability management • Executive reporting and KPI tracking

Example: Get security risk analysis for certificate expiry management

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jsonNoReturn structured JSON format for programmatic analysis and dashboard integration. Use TRUE for automated reporting and data processing
actionYesAnalytics and monitoring action to perform. SUPPORTED ACTIONS: 'get' (retrieve comprehensive monitoring data, usage statistics, and performance metrics for the entire infrastructure)
uid_tokenNoUniversal identity authentication token. Only required when using universal_identity authentication instead of standard API key authentication
filter_by_riskNoFilter certificate and security risk analysis. OPTIONS: 'Expired' (certificates past expiry), 'Healthy' (certificates within validity), 'Expiring Soon' (certificates near expiry)
filter_by_typeNoFocus on specific item categories. SUPPORTED TYPES: 'Targets', 'Static Secrets', 'Dynamic Secrets', 'DFC Key', 'Roles', 'Auth Methods', 'Rotated Secrets', 'Certificates'. Use exact match for filtering
filter_by_productNoFilter by Akeyless product components. OPTIONS: 'sm' (Secrets Management), 'adp' (Advanced Data Protection), 'sra' (Secure Remote Access). Essential for multi-product environments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description carries the burden. It describes what data is retrieved and the filtering options, but it does not explicitly state that the tool is read-only or non-mutating, nor does it mention pagination, rate limits, or error behavior. The 'get' action implies a safe read operation, but this is not explicitly disclosed.

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?

The description is well-structured with clear sections (SUPPORTED ACTIONS, ANALYTICS COVERAGE, FILTERING OPTIONS, USE CASES, Example). While somewhat verbose, each section provides useful information and the example adds practical clarity. No significant redundancy.

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

Completeness4/5

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

Given the tool's complexity (6 params, output schema), the description covers all major elements: supported actions, data coverage, filtering, use cases, and a usage example. It doesn't explain whether filters can be combined or specify output format, but the output schema is available. This is sufficient for tool selection and basic usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by elaborating on filter options with examples, noting that filter_by_type uses exact match, and that filter_by_product is essential for multi-product environments. It also explains the 'get' action in context, going beyond the schema descriptions.

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?

The description clearly identifies 'ANALYTICS & MONITORING TOOL' and defines the supported action 'get' as retrieving comprehensive monitoring data, usage statistics, and performance metrics. This distinguishes it from sibling management tools by focusing on analytics and reporting rather than resource management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'USE CASES' section lists SOC dashboards, compliance reporting, capacity planning, risk assessment, and executive reporting, providing clear when-to-use context. It doesn't explicitly exclude alternatives but the analytics focus is unique among the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sanyambassi/thales-cdsp-csm-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server