Indicate
Server Details
AI-powered intelligence for your development workflow via Indicate.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- OAuth
- Not connectable
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose in a sequential workflow: health_check verifies connectivity, list_tenants lists accessible tenants, list_data_sources lists data sources within a tenant, list_metrics lists metrics for a data source, and query_metric fetches time-series data. There is no overlap or ambiguity in their functions.
All tool names follow a consistent verb_noun pattern (e.g., health_check, list_tenants, list_data_sources, list_metrics, query_metric). The naming is uniform and predictable, using snake_case throughout with clear action descriptors.
With 5 tools, the set is well-scoped for the Indicate system's purpose of data querying and management. Each tool serves a specific step in the workflow, from authentication to data retrieval, and none feel redundant or missing for the domain.
The tool set covers the core workflow steps (connectivity, tenant listing, data source listing, metric listing, and data querying) effectively. A minor gap exists in lacking tools for creating or updating resources (e.g., adding tenants or data sources), but the provided tools allow agents to navigate and query data without dead ends.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
- Changed
list_data_sources3 fields changed- removed
Output schema / $defs / DataSourceSummary / properties / boundedContextRemoved value: -{ - "title": "Boundedcontext", - "type": "string" -} - added
Output schema / $defs / DataSourceSummary / properties / semanticContextIdAdded value: +{ + "title": "Semanticcontextid", + "type": "string" +} - changed
Output schema / $defs / DataSourceSummary / requiredPrevious value: -[ - "id", - "boundedContext", - "displayName" -]New value: +[ + "id", + "semanticContextId", + "displayName" +]
- Changed
list_metrics7 fields changed- removed
Input schema / properties / bounded_contextRemoved value: -{ - "description": "Bounded context ID from the 'bounded_context' field in the list_data_sources response.", - "title": "Bounded Context", - "type": "string" -} - added
Input schema / properties / semantic_context_idAdded value: +{ + "description": "Bounded context ID from the 'semantic_context_id' field in the list_data_sources response.", + "title": "Semantic Context Id", + "type": "string" +} - changed
Input schema / requiredPrevious value: -[ - "tenant_id", - "data_source_id", - "bounded_context" -]New value: +[ + "tenant_id", + "data_source_id", + "semantic_context_id" +] - removed
Output schema / $defs / Dimension / properties / boundedContextRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null, - "title": "Boundedcontext" -} - added
Output schema / $defs / Dimension / properties / semanticContextIdAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Semanticcontextid" +} - removed
Output schema / $defs / Metric / properties / boundedContextRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null, - "title": "Boundedcontext" -} - added
Output schema / $defs / Metric / properties / semanticContextIdAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Semanticcontextid" +}
- Changed
query_metric2 fields changed- removed
Input schema / properties / bounded_contextRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Bounded context ID (for reference / logging).", - "title": "Bounded Context" -} - added
Input schema / properties / semantic_context_idAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Bounded context ID (for reference / logging).", + "title": "Semantic Context Id" +}
5 tool updates
- First observed
health_check - First observed
list_data_sources - First observed
list_metrics - First observed
list_tenants - First observed
query_metric
Related MCP Connectors
The AI orchestration agent for modern software teams.
Codebase intelligence for AI agents — dead code, blast radius, ownership.
Direct access to Cypress tests results and accessibility reports in your AI workflow.
Your team's shipping standards, org map and delivery metrics, inside your coding agent.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants like Claude Code and Cursor to get evidence-based tool and workflow recommendations from community data.MIT
- AlicenseNot gradedqualityCmaintenanceConnect engineering metrics, DORA performance, deploy risk scoring, and PR health to any AI assistant. Score PRs for deployment risk using a 36-signal model, query team health, incidents, coverage, and more.MIT
- AlicenseNot gradedqualityDmaintenanceEnables end-to-end automation of developer workflows from Jira issue tracking to GitHub pull requests through natural language, allowing developers to search issues, create branches, commit changes, and manage PRs directly from their IDE.2MIT
- FlicenseNot gradedqualityDmaintenanceEnhances AI-assisted development with intelligent context, team awareness, and automated workflow orchestration, enabling a senior developer-like pair programming experience.-
Glama MCP Gateway
Add one secure layer between your agents and this server.