Skip to main content
Glama

Lagged autocorrelation

bpj_series_autocorrelation
Read-onlyIdempotent

Use the full-series mean and total squared deviation to compute autocorrelation at a given lag.

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": {
      "values": "<values>",
      "lag": "<lag>"
    },
    "name": "bpj_series_autocorrelation"
  }
}

Input Schema

NameRequiredDescriptionDefault
lagYes
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 a closed-world profile, so the safety burden is covered. The description adds the estimator convention (mean and denominator computed over the full series, i.e. not pairwise-complete or lag-adjusted), which is genuinely useful, but says nothing about error behavior when lag exceeds series length or about the output value's range.

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?

A single front-loaded sentence with no filler; the verb 'compute' leads. It is tight but slightly impenetrable in its wording, spending its only sentence on method rather than on how to call it.

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 simple two-parameter read-only tool with no output schema, the description is minimally adequate: it names the operation and estimator. Missing input-format guidance for 'values', the lag-vs-length precondition, and any hint of the returned coefficient's scale leave real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it largely does not. It never explains that 'values' is a JSON-encoded numeric array string within 12,000 characters, nor the constraint that lag (1-499) must be smaller than the series length.

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?

States a specific verb and resource: compute autocorrelation at a given lag, and adds the estimator detail (full-series mean and total squared deviation). An agent can identify the operation, though nothing distinguishes it from siblings such as bpj_series_lag_differences.

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?

Usage is only implied by the phrase 'at a given lag'; there is no explicit when-to-use, no prerequisites, and no named alternative among the many sibling series tools. The agent must infer that this is a single-lag ACF rather than a lag-difference or smoothing operation.

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.