Skip to main content
Glama

Performance diagnose

performance_diagnose
Read-onlyIdempotent

Compares two equal-length, non-overlapping historical periods from one saved account snapshot (the performance-diagnosis method). Takes the exact account ID and dates of the request, computes coverage and changes, and separates facts, unknowns and the next check. Missing rows are not counted as zero, and generic results are not counted as purchases. responseMode=answer returns a verified report; evidence returns the underlying data. No writes.

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": {
      "input": "<input>"
    },
    "name": "performance_diagnose"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
accountIdsNoOptional account selection; can only narrow this workspace's access.
userStatementNoRequired for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence.
idempotencyKeyNoRequired for mutations. Reuse the same key only when retrying the exact same call; a completed outcome is applied once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / userStatement / description
      Previous value: -"Required for launch_brief: the latest verbatim user request or free-text answer. Otherwise optional user-provided context, treated as an unverified user statement, never permission or verified platform evidence."New value: +"Required for launch_brief: the user's request or answer for this launch, in their own words. Otherwise optional: the user's request for this call, treated as an unverified user statement, never permission or verified platform evidence."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety burden is covered. The description still adds real behavioral content beyond them: coverage is computed and reported, missing rows are not treated as zero, generic results are not counted as purchases, and the output is a facts/unknowns/next-check report. It does not disclose ordering, performance limits, or snapshot freshness.

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 method and scope are front-loaded in the first sentence, and the no-writes disclaimer closes cleanly. It is dense but every clause carries information; the middle sentence is slightly compressed jargon ('computes coverage and changes, and separates facts, unknowns and the next check') that costs a little readability.

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 nested-object tool with no output schema, the description does the important work: it states the input shape, the comparison invariant, the methodological caveats, and what each responseMode returns. Remaining gaps are the contents/shape of the 'verified report' and the handling of actionType and campaignId filtering.

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?

With schema description coverage at 75%, the schema already documents accountId, actionType, responseMode, and the before/after periods. The description reinforces the equal-length/non-overlapping constraint and the two response modes but adds little new meaning — notably it never explains campaignId, which is undocumented in both places, and the multi-account/collection path that triggers evidence mode.

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 opening sentence names a specific verb and resource — comparing two equal-length, non-overlapping historical periods from one saved account snapshot — and labels it a named method (performance-diagnosis). That is enough for an agent to distinguish it from simple retrievals like metrics_daily or performance_period, though it never explicitly contrasts itself with the closer sibling metric_compare.

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 does give one explicit routing rule — answer mode for diagnostic/outcome reviews, evidence only for an additional deliverable or multi-account collection — which is genuine when-to-use guidance. However, it never says when this tool is preferable to performance_period, metric_compare, or saas_performance, so alternative selection is left to inference.

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.