Skip to main content
Glama
scoutapp

Scout Monitoring MCP

Official

get_endpoint_metrics

Retrieve a single timeseries metric, such as response time or throughput, for a specific application endpoint over a given time range.

Instructions

Get a single timeseries metric for a specific endpoint in an application.

Args:
    app_id (int): The ID of the Scout APM application.
    endpoint (str): The endpoint path (e.g., "/users", "/orders").
    metric (str): The metric to retrieve (e.g., "response_time", "throughput").
    from_ (str): The start datetime in ISO 8601 format.
    to (str): The end datetime in ISO 8601 format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYes
endpointYes
metricYes
from_Yes
toYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description carries the burden of behavioral disclosure. It implies a read operation but does not mention auth, rate limits, return format, or any edge cases. The description is silent on most behavioral traits.

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 concise with a clear header and a structured list. No extraneous text. However, the parameter list could be integrated more naturally, and the description is slightly terse.

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

Completeness3/5

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

Given the tool's simplicity and presence of an output schema, the description adequately covers the main action. However, it lacks details about time range constraints, data granularity, or empty result handling.

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?

The description adds meaningful explanations for all 5 parameters (e.g., 'The ID of the Scout APM application.'), which goes beyond the schema's bare titles. This compensates for the low schema description coverage.

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 states the tool retrieves a single timeseries metric for a specific endpoint, using a specific verb and resource. It does not explicitly differentiate from sibling tools like get_app_metrics, but the specificity reduces ambiguity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., get_app_metrics for multiple metrics). There are no conditionals or exclusions mentioned.

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/scoutapp/scout-mcp-local'

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