Skip to main content
Glama

DevTune MCP

by ai.devtune
OverviewDiscussionsAdmin

devtune_get_outcomes_ledger

Get measured actions with authoritative improved, mixed, no_clear_change, declined, still_measuring and unmeasured results, the evidence behind each result (counts, active days, exposure and the chance of a shift that large), and a conclusive-measurement improvement rate. Reporting windows filter actions; comparisons use fixed 14-day before/after windows. Each item includes overlappingActions per page and comparison window, listing other completed actions with actionId, title and completedAt. With interventionId, top-level overlappingActions covers that measurement’s 7, 14, 30 and 90 day comparisons, even outside the selected ledger cohort. Each comparison has state available with an actions array, or unavailable with actions null if the supplementary check failed; measurements still load. Shared page movement cannot be attributed to this action alone. Also returns analytics-attributed conversions for fixed 30 and 90 day windows. If the measurement detail read fails, top-level overlappingActions contains one unavailable entry with actions=null and no page/window metadata. Redirect-shipped missing-page actions include evidence.redirect404 with requestedPath, hosts, before/after 404 request counts and fixed-window bounds, status-coverage day counts, source and generation. Its state uses 404 rows observed before each capture: stopped (observed before, none after), still_happening (observed in both), or unmeasured (incomplete status coverage, unknown request hosts, open window or no baseline 404s). A later counter increase nulls that count with reason counter_changed and preserves a known state. Both windows require coverage on every UTC date for every requested host; the browser snippet cannot measure 404s. This separate metric never changes the overall result. A saved suggested destination identifies a redirect; a saved requested URL requires an observed 3xx response and no 2xx responses across the requested hosts after the window closes. Other actions omit the field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoOpaque cursor from the previous response; cursors expire after ~48 hours.
sourceNoFilter Actions and Outcomes by source; both is the default
statusNo
pageSizeNoResults per page (1-100). Defaults to 25.
windowDaysNoFixed rolling window in days: 7, 30, 90, or 365. Defaults to 30.
interventionIdNoInclude 7, 14, 30 and 90 day impact windows (citations, presence and answer fetches) for this completion-based measurement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Filter Actions and Outcomes by source; both is the default",
+  "enum": [
+    "ai_search",
+    "agent_picks",
+    "both"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / interventionId / description
      Previous value: -"Include 7, 14, 30 and 90 day impact windows for this completion-based measurement."New value: +"Include 7, 14, 30 and 90 day impact windows (citations, presence and answer fetches) for this completion-based measurement."
  3. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "measured",
-  "in_flight",
-  "blind",
-  "unmatched_url",
-  "sensor_gap",
-  "win",
-  "loss",
-  "still_measuring",
-  "unmeasured",
-  "conclusive"
-]New value: +[
+  "measured",
+  "in_flight",
+  "blind",
+  "unmatched_url",
+  "sensor_gap",
+  "improved",
+  "mixed",
+  "no_clear_change",
+  "declined",
+  "still_measuring",
+  "unmeasured",
+  "conclusive"
+]
  4. Changed1 schema field changed
    • addedInput schema / properties / interventionId
      Added value: +{
+  "description": "Include 7, 14, 30 and 90 day impact windows for this completion-based measurement.",
+  "format": "uuid",
+  "type": "string"
+}
  5. First observed

TDQS

A3.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so extensively: fixed 14-day before/after comparison windows, overlappingActions scope with and without interventionId, available/unavailable comparison states, the 'shared page movement cannot be attributed to this action alone' caveat, and the redirect404 state machine including counter_changed nulling and coverage requirements. This is unusually rich behavioral disclosure.

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

Conciseness2/5

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

The description is a single ~450-word wall of text with no paragraph breaks, front-loading the purpose but then burying it under redirect404 minutiae, state enumerations, and edge-case handling. Much of the redirect-404 detail is implementation trivia rather than selection/invocation guidance, so many sentences do not earn their place.

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?

There is no output schema, so the description must explain return values, and it does so thoroughly (evidence fields, overlappingActions, comparison states, analytics-attributed conversions, redirect404 evidence). It is nearly complete for a complex read tool, missing only usage/routing context relative to siblings.

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 83%, so the schema already documents cursor, source, pageSize, and status. The description adds genuine meaning for interventionId ('covers that measurement's 7, 14, 30 and 90 day comparisons, even outside the selected ledger cohort') and residual window behavior, but most parameters are fully covered by the schema, keeping this near the baseline.

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 gives a specific verb and resource: 'Get measured actions' with their authoritative result categories, evidence, and a conclusive-measurement improvement rate. It is distinctive from generic reads like devtune_get_actions or devtune_get_what_works, though it never names or contrasts those siblings directly.

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 explicit when-to-use guidance, no when-not-to-use statement, and no reference to the many sibling tools that also surface action/outcome data (devtune_get_actions, devtune_get_what_works, devtune_get_direct_lift). Window/filter behavior is described, but nothing tells the agent when this ledger is the right call over an alternative.

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

All DevTune MCP toolsInspect
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