Skip to main content
Glama
Sign In

Nuira

by ai.nuira
OverviewDiscussionsAdmin

Performance summary

get_summary
Read-onlyIdempotent

Headline figures for the current period: revenue, ad spend, contribution and blended ROAS, each with the change against the previous period, plus new and returning customers, order count, sessions and conversion rate. Use this first for any question about overall performance, and for how many customers are new or returning. Then drill down: get_series for day by day, get_channels per channel, get_contribution_breakdown for COGS and gross profit. Optional from and to (inclusive YYYY-MM-DD, both or neither, never after today) read another span instead of the default period. A named month, a week or two dates the operator gave MUST be sent here: without them this reads the last 30 days, which is not that month.

Input Schema

NameRequiredDescriptionDefault
toNoLast day of the span, inclusive, as YYYY-MM-DD; not after today. Send together with `from`, or omit both to read the default 30-day period.
fromNoFirst day of the span, inclusive, as YYYY-MM-DD. Send together with `to`, or omit both to read the default 30-day period.
compareNoWhat to compare the span with: previous (default, the same number of days just before), yoy (the same dates last year) or yoyWeekday (52 weeks back, the same weekdays — use it for natural Monday–Sunday weeks or whenever the operator says 'last year' over weeks).
salesChannelNoOnly online orders (the web shop) or only point-of-sale orders; omit for every channel. When the operator says 'solo web', 'online only' or 'sin POS', send online — and keep sending it for the rest of the conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / compare
      Added value: +{
+  "description": "What to compare the span with: previous (default, the same number of days just before), yoy (the same dates last year) or yoyWeekday (52 weeks back, the same weekdays — use it for natural Monday–Sunday weeks or whenever the operator says 'last year' over weeks).",
+  "enum": [
+    "previous",
+    "yoy",
+    "yoyWeekday"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / salesChannel
      Added value: +{
+  "description": "Only online orders (the web shop) or only point-of-sale orders; omit for every channel. When the operator says 'solo web', 'online only' or 'sin POS', send online — and keep sending it for the rest of the conversation.",
+  "enum": [
+    "online",
+    "pos"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / from / description
      Added value: +"First day of the span, inclusive, as YYYY-MM-DD. Send together with `to`, or omit both to read the default 30-day period."
    • addedInput schema / properties / to / description
      Added value: +"Last day of the span, inclusive, as YYYY-MM-DD; not after today. Send together with `from`, or omit both to read the default 30-day period."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: the default is the last 30 days, `from`/`to` must be sent together, and dates can never be after today. It does not discuss caching or latency, but that is minor for a read-only summary.

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?

Front-loaded with what it returns, then usage routing, then date semantics – a sensible order with no filler sentences. It is dense and somewhat long, with a bit of overlap between the metric list and the parameter paragraph, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating the returned figures and the comparison-to-previous-period behavior. It also states the default period and the drill-down siblings, so an agent has everything needed to call it correctly and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds decision rules the schema does not: both-or-neither for `from`/`to`, never after today, and the critical warning that omitting them silently reads 30 days instead of the requested month. That meaningfully changes how an agent fills the parameters.

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?

Names a specific verb+resource and enumerates the exact headline metrics returned (revenue, ad spend, contribution, blended ROAS, new/returning customers, order count, sessions, conversion rate). It is clearly distinguishable from narrower siblings like get_channels or get_series.

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

Usage Guidelines5/5

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

Explicitly says to use this first for any overall-performance question and for new-vs-returning customers, then routes to get_series, get_channels and get_contribution_breakdown for drill-downs. It also states a hard requirement that operator-supplied dates MUST be passed here rather than relying on the default 30-day window.

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

All Nuira 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