Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

mureo_state_report_set

Persist structured analysis reports into STATE.json so the dashboard can render the latest summary without re-running the agent.

Instructions

Atomically persist a structured analysis report summary into STATE.json's reports section so the read-only configure dashboard can render the latest report without re-running the agent. report selects the kind — one per skill, listed below; summary carries generated_at (ISO 8601), period, totals (headline figures), flags (one entry per finding) and narrative (the judgement and the proposal). Each part is rendered as what it is — figures as figures, flags as chips, narrative as prose — so a summary that folds all of it into the narrative renders as one unreadable paragraph, and the narrative bound below is enforced. Other report kinds are preserved. Best-effort: a skill should skip this silently where the context MCP is unavailable. Returns the updated state document.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOptional path to the file. Defaults to STRATEGY.md / STATE.json in the MCP server's current working directory. Paths outside cwd are refused.
reportYesReport kind: ``daily`` (daily-check), ``weekly`` (weekly-report), ``monthly`` (monthly-report), ``goal`` (goal-review), ``audience`` (audience-review), ``experiment`` (experiment), ``fatigue`` (ad-fatigue-check), ``pacing`` (budget-pacing), ``tracking`` (tracking-health).
summaryYesWrite the structure, not one paragraph. Headline figures go in ``totals`` (spend, conversions, cpa, ctr, clicks, impressions) as raw numbers — 773957, not "¥773,957"; 0.0466, not "4.66%". Each finding goes in ``flags`` as its own entry, with the detail in its ``params``. ``narrative`` keeps only the judgement and the proposal, at most 400 characters: a longer one is refused, never truncated, because a sentence cut in half is worse than a long one. Fields: generated_at (ISO 8601), period, totals (the headline figures above), kpis (the OPTIONAL per-platform split — the breakdown, not the headline row), flags, narrative. Each flag is either a legacy snake_case string OR a structured object {code, severity, params}: code is a canonical vocabulary key (e.g. goals_met, invalid_traffic_suspected, budget_drift, zero_cv_adspots, spend_spike, anomaly_baseline_insufficient), severity is action|watch|info|positive (defaulted from code if omitted), and params holds the detail (adspot ids, yen, ctr) — keep detail in params, NOT in the code and NOT in the narrative. For a finding outside the vocabulary use {code:'custom', severity, label} where label is a string or {locale: text} map. Unknown non-custom codes are rejected.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.13.1
    • changedInput schema / properties / report / description
      Previous value: -"Report kind: ``daily`` (daily-check), ``weekly`` (weekly-report), or ``goal`` (goal-review)."New value: +"Report kind: ``daily`` (daily-check), ``weekly`` (weekly-report), ``monthly`` (monthly-report), ``goal`` (goal-review), ``audience`` (audience-review), ``experiment`` (experiment), ``fatigue`` (ad-fatigue-check), ``pacing`` (budget-pacing), ``tracking`` (tracking-health)."
    • changedInput schema / properties / report / enum
      Previous value: -[
-  "daily",
-  "weekly",
-  "goal"
-]New value: +[
+  "daily",
+  "weekly",
+  "monthly",
+  "goal",
+  "audience",
+  "experiment",
+  "fatigue",
+  "pacing",
+  "tracking"
+]
    • changedInput schema / properties / summary / description
      Previous value: -"Free-form summary object. Convention: generated_at (ISO 8601), period, kpis (per-platform / totals headline numbers), flags, narrative (short text). Each flag is either a legacy snake_case string OR a structured object {code, severity, params}: code is a canonical vocabulary key (e.g. goals_met, invalid_traffic_suspected, budget_drift, zero_cv_adspots, spend_spike, anomaly_baseline_insufficient), severity is action|watch|info|positive (defaulted from code if omitted), and params holds the detail (adspot ids, yen, ctr) — keep detail in params / narrative, NOT in the code. For a finding outside the vocabulary use {code:'custom', severity, label} where label is a string or {locale: text} map. Unknown non-custom codes are rejected."New value: +"Write the structure, not one paragraph. Headline figures go in ``totals`` (spend, conversions, cpa, ctr, clicks, impressions) as raw numbers — 773957, not \"¥773,957\"; 0.0466, not \"4.66%\". Each finding goes in ``flags`` as its own entry, with the detail in its ``params``. ``narrative`` keeps only the judgement and the proposal, at most 400 characters: a longer one is refused, never truncated, because a sentence cut in half is worse than a long one. Fields: generated_at (ISO 8601), period, totals (the headline figures above), kpis (the OPTIONAL per-platform split — the breakdown, not the headline row), flags, narrative. Each flag is either a legacy snake_case string OR a structured object {code, severity, params}: code is a canonical vocabulary key (e.g. goals_met, invalid_traffic_suspected, budget_drift, zero_cv_adspots, spend_spike, anomaly_baseline_insufficient), severity is action|watch|info|positive (defaulted from code if omitted), and params holds the detail (adspot ids, yen, ctr) — keep detail in params, NOT in the code and NOT in the narrative. For a finding outside the vocabulary use {code:'custom', severity, label} where label is a string or {locale: text} map. Unknown non-custom codes are rejected."
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changedv0.10.27
    • changedInput schema / properties / summary / description
      Previous value: -"Free-form summary object. Convention: generated_at (ISO 8601), period, kpis (per-platform / totals headline numbers), flags (list of notable items), narrative (short text)."New value: +"Free-form summary object. Convention: generated_at (ISO 8601), period, kpis (per-platform / totals headline numbers), flags, narrative (short text). Each flag is either a legacy snake_case string OR a structured object {code, severity, params}: code is a canonical vocabulary key (e.g. goals_met, invalid_traffic_suspected, budget_drift, zero_cv_adspots, spend_spike, anomaly_baseline_insufficient), severity is action|watch|info|positive (defaulted from code if omitted), and params holds the detail (adspot ids, yen, ctr) — keep detail in params / narrative, NOT in the code. For a finding outside the vocabulary use {code:'custom', severity, label} where label is a string or {locale: text} map. Unknown non-custom codes are rejected."
  4. Addedv0.10.7

TDQS

A4.1/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 of behavioral disclosure. It reveals atomicity, preservation of other report kinds, best-effort skipping when context MCP is unavailable, and the return of the updated state document. These are important behavioral traits.

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 verbose and repeats schema content (e.g., the summary structure, code vocabulary). It could be substantially trimmed while retaining the essential purpose and behavior notes. Several sentences duplicate parameter descriptions rather than contributing new information.

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?

The description covers the tool's purpose, behavior, return value, and edge cases like best-effort skipping. It does not explicitly discuss error conditions beyond code rejection (covered in schema), but overall it provides sufficient context for a typical use case despite the absence of an output schema.

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?

The schema descriptions for all three parameters are already exhaustive (100% coverage). The tool description largely repeats the same details about report kinds, summary structure, and validation rules, adding no new meaning beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: atomically persist a structured analysis summary into STATE.json's reports section. It also specifies the intended benefit (rendering in the read-only configure dashboard) and distinguishes it from other state-related tools by its specific action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it (when a report summary needs to be stored) and provides context about the dashboard, but it does not explicitly contrast with alternative tools like mureo_state_get or mureo_state_upsert_campaign. No explicit when-not-to-use guidance is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server