Skip to main content
Glama
Coval MCP Server

Coval MCP Server

Official
by coval-ai

Get metric

get_metric
Read-onlyIdempotent

Retrieve detailed information about a specific metric, including its type, description, and configuration, by providing the unique metric ID.

Instructions

Get detailed information about a specific metric. Shows metric type, description, and configuration.

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": {
      "metric_id": "<metric_id>"
    },
    "name": "get_metric"
  }
}

Input Schema

NameRequiredDescriptionDefault
metric_idYesThe unique ID of the metric to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.1
    • changedInput schema / properties / metric_id / description
      Previous value: -"The unique ID of the metric to retrieve. Get this from list_metrics."New value: +"The unique ID of the metric to retrieve."
    • addedInput schema / properties / metric_id / maxLength
      Added value: +128
    • addedInput schema / properties / metric_id / pattern
      Added value: +"^[A-Za-z0-9_-]+$"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context about what is returned (metric type, description, configuration), but does not cover error behavior, permissions, or rate limits.

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

Conciseness5/5

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

The description is two short sentences, front-loaded with the core action and followed by the return contents. Every sentence contributes useful information with no filler.

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?

For a simple one-parameter read tool with complete schema coverage and clear annotations, the description is largely sufficient. It identifies the main returned fields but does not describe behavior when the metric ID is invalid or missing.

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?

The single parameter metric_id is fully documented in the schema with pattern, length constraints, and a clear description. The tool description adds no parameter-level semantics beyond what the schema already provides, so baseline 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 states a specific verb and resource: retrieving detailed information about one metric. It implicitly contrasts with list_metrics by saying 'a specific metric,' but it does not explicitly name the sibling tool for listing metrics.

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?

Use is implied for fetching an individual metric by ID, but the description does not explicitly say when to use this instead of list_metrics or other alternatives. No exclusions or prerequisites are given.

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