Scribase

metrics.get

Read-onlyIdempotent

Get environment metrics. GET .../metrics. Optional period: the window the server accepts (e.g. 1h, 24h, 7d).

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": {
      "organization_id": "<organization_id>",
      "project_id": "<project_id>",
      "environment_id": "<environment_id>"
    },
    "name": "metrics.get"
  }
}

Input Schema

Name	Required	Description
`period`	No	Time window, e.g. 1h, 24h, 7d
`project_id`	Yes	project_id (required)
`environment_id`	Yes	environment_id (required)
`organization_id`	Yes	organization_id (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds the endpoint path and the fact that the server only accepts certain window values, but says nothing about aggregation granularity, retention limits, or rate limits, which matter for a metrics read.

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?

Three short sentences with the purpose front-loaded and no filler paragraphs. The 'GET .../metrics' line and the repeated period examples are low-value restatements, but they cost little.

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?

For a four-parameter, three-required read tool with no output schema, the definition is minimally adequate: it identifies the resource and the one optional knob. It leaves unclear what metrics are actually returned and at what granularity, which an agent needs in order to choose this over analytics.summary or usage.get.

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?

Schema description coverage is 100%, so all four parameters are already documented, and the description's period examples ('1h, 24h, 7d') duplicate the schema text verbatim. The phrase 'the window the server accepts' adds a mild hint that values are server-validated, but no default, maximum, or accepted value list is given.

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 ('Get environment metrics') and pins the underlying endpoint, so an agent knows this is a read of environment-level telemetry. It does not distinguish itself from closely related siblings such as usage.get, analytics.summary, insights.get, or uptime.status, which all plausibly return similar data.

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?

There is no when-to-use guidance at all: no statement of what question this tool answers, no exclusions, and no pointer to the alternative metrics/analytics siblings. The only contextual sentence is about the period parameter, not about tool selection.

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

All Scribase tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?