Skip to main content
Glama

launchfiles_domain_horizon_memory

Read-onlyIdempotent

Recall longitudinal multi-run audit memory across Clarity, UX, Search/GSC, Checkout Drift, and Directory Distribution (distributionHistory) for a domain, surfacing verified shipped-change deltas, cross-vertical self-challenges, and the next highest-leverage bet.

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": {
      "url": "<url>"
    },
    "name": "launchfiles_domain_horizon_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or https:// URL to inspect longitudinal horizon memory for.
run_fresh_drift_checkNoOptionally run and persist a fresh live checkout/trust drift check before computing horizon memory (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the useful detail that the memory spans five named audit verticals and reports shipped-change deltas, but it omits the important behavioral nuance that run_fresh_drift_check persists a fresh drift check — a state-changing side effect left entirely to the schema — and says nothing about history depth or behavior when no prior runs exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence starting with the operative verb, which is good structure. However, the long parenthetical enumeration and the marketing-flavored tail ('cross-vertical self-challenges', 'next highest-leverage bet') add length without adding precision.

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 two-parameter read tool with full schema coverage and no output schema, the description covers the broad subject areas of the return value, which is adequate. It still leaves gaps an agent needs: what a 'verified shipped-change delta' concretely is, how far back memory extends, and what happens when no history exists for the domain.

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 coverage is 100%, so both parameters are already documented in structured form, and the description contributes only the vague framing 'for a domain'. It never mentions run_fresh_drift_check, so it adds no meaning beyond the schema's own explanation of that flag.

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 gives a specific verb ('Recall') and a specific resource ('longitudinal multi-run audit memory across Clarity, UX, Search/GSC, Checkout Drift, and Directory Distribution'), which clearly separates it from the single-run audit siblings. It stops short of naming an alternative tool, and phrases like 'cross-vertical self-challenges' and 'next highest-leverage bet' blur what the resource actually is.

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: 'longitudinal multi-run' and 'shipped-change deltas' suggest calling this before or after fresh audits rather than instead of them, but no when-to-use, when-not, or alternative is stated. The existence of launchfiles_live_drift_check and the run_fresh_drift_check parameter hint at a relationship that the description never spells out.

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.