Skip to main content
Glama
Sign In

Marsell

by com.getmarsell
OverviewDiscussionsAdmin

Outcomes summary

outcomes_summary
Read-only

Reports what each piece of the plan's work produced against its forecast over the last days: per row its id, title, kind, channel, state, forecast, totals by metric (visits, sign-ups, orders, revenue, reach, opens, clicks and the rest), status (behind, on, ahead, or unknown when nothing was measured) and whether any number was attributed to it; then the totals by channel and by kind, and how many rows are behind, on, ahead or unknown. Use it to judge the plan's work; one row whole is work_get, a business-wide number day by day is metrics_series, and the Analytics place (place_open analytics) has every number. Only numbers attributed to a piece of work count here.

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": {
      "days": "<days>"
    },
    "name": "outcomes_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysYesThe span, in days ending today (7 for the week, 30 for the month).
projectNoThe project's id or exact name. Optional when the account has one project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only and closed-world safety, so the description adds real value beyond them: it defines the 'unknown' status as nothing measured, discloses that attribution is the inclusion criterion, and warns that unattributed numbers are excluded. It does not mention result size, pagination, or cost, which keeps it off a 5.

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?

The first sentence is a long run-on that spends many words enumerating metrics ('visits, sign-ups, orders, revenue, reach, opens, clicks and the rest') only to end in 'and the rest', which weakens the list. The routing guidance that follows is tight and front-loaded, but the payload description could be pruned substantially.

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?

There is no output schema, so the description carries the full burden of explaining returns — and it does, covering row-level fields, per-metric totals, status categories, attribution flag, channel/kind rollups, and status counts. An agent knows what it will get and how to interpret 'unknown'.

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 100% and both parameters are documented in-schema, so baseline 3 applies. The description only echoes the window ('over the last days') and the plan scoping, adding no format or edge-case guidance for `project` beyond what the schema already says.

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?

Opens with a specific verb and resource: reports per-row outputs versus forecast, enumerates the returned fields, and adds channel/kind rollups. It names the siblings it is not (work_get, metrics_series, place_open analytics), so the tool is distinguishable without opening any schema.

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?

'Use it to judge the plan's work' states the intended job, then routes the agent explicitly: one whole row is work_get, a business-wide daily number is metrics_series, all numbers live in the Analytics place. It also gives a hard inclusion rule — only attributed numbers count — which prevents a common misuse.

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

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