Skip to main content
Glama
scoutapp

Scout Monitoring MCP

Official

get_app_endpoints

Retrieve all endpoints for an application with aggregated performance metrics including throughput, latency, and error rates within a specified time window. Identify high-traffic or problematic endpoints for further analysis.

Instructions

Get all endpoints for a specific application. Also gets aggregated performance
metrics withing the window of "from_" to "to". Useful for identifying high
throughput, high latency or high error rate endpoints accross the application with a
single call.

These endpoints can be used in other tools to fetch endpoint-specific metrics,
traces or errors.

Args:
    app_id (int): The ID of the Scout APM application.
    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
from_Yes
toYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It accurately describes a read operation (getting endpoints and metrics) with no side effects mentioned. It does not discuss permissions or rate limits, but for a simple read tool, the description is adequate.

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 front-loaded with purpose and includes a helpful note about reuse. The Args section is somewhat verbose but adds necessary detail. Overall, it's concise enough without missing key information.

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 that an output schema exists (not shown), the description does not need to detail return values. It covers the tool's purpose, parameters, and usage context well, though it could mention what the aggregated metrics look like or any pagination.

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 description coverage is 0%, but the description explains all three parameters (app_id, from_, to) in detail, adding meaning beyond the schema titles. It specifies that from_ and to are ISO 8601 datetimes.

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 states the tool gets all endpoints for an application and also aggregated performance metrics. This distinguishes it from siblings like get_app_endpoint_traces (traces) and get_app_metrics (metrics only).

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?

The description hints at when to use the tool (identifying high throughput, latency, error rate) and mentions endpoints can be used in other tools. However, it does not explicitly state when not to use or compare against alternatives like get_app_endpoint_traces.

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