Skip to main content
Glama

Get monitoring

get_monitoring
Read-only

Which monitoring a project is connected to — its Grafana's address, the Prometheus data source queries go to, whose token it is (a Grafana service account with the Viewer role) and whether it is switched on; 'secretSet' says a token is held, the token itself never comes back. 'connected' false means none: whoever administers the project connects it on the board's Monitoring sheet at 'url' — the token is entered there, never in this chat. 'questions' lists the ready-made questions (monitoring_hosts) with the PromQL each runs, and 'tools' what can be read. Any member of the project may ask.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectKey": "<projectKey>"
    },
    "name": "get_monitoring"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectKeyYesProject key, e.g. 'PM'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavioral context: secrets are indicated only by 'secretSet', the token is never returned or entered in chat, disconnected projects must be connected by an administrator on the Monitoring sheet, and any project member may ask. This is substantial transparency for a safe read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description contains useful information, but it is delivered as a dense, semicolon-heavy paragraph with some repetition around the token never being exposed. It is not badly bloated, but it could be front-loaded and structured more clearly for faster scanning.

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

Completeness5/5

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

With no output schema, the description carries the full burden of explaining return semantics, and it does so thoroughly: connection details, secret handling, disconnected state, questions, and tools are all covered. An agent has enough context to interpret the response correctly.

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

Parameters3/5

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

There is only one parameter, projectKey, and the schema already documents it at 100% coverage with an example value. The description does not add any further meaning or constraints for projectKey beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource: a project's monitoring connection, including Grafana address, Prometheus data source, token identity, enabled status, ready-made questions, and available tools. It references monitoring_hosts explicitly, but it does not directly distinguish its role from monitoring_query or monitoring_alerts beyond describing the return contents.

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

Usage Guidelines3/5

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

Usage is implied: inspect how a project is connected to monitoring. The description gives useful operational guidance for the 'connected' false case and notes that any project member may ask, but it does not state when to choose this tool over monitoring_query, monitoring_alerts, or monitoring_dashboards.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources