Skip to main content
Glama
Sign In

Moatlight

by com.moatlight
OverviewDiscussionsAdmin

The ranked plan of changes and the questions you lost

get_report_actions
Read-only

For a finished report: up to three ranked moves (reason, exact edit, page, effort) and, for each buyer question AI answered with a rival, who won and why. Needs login with scope reports:read.

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": {
      "reportId": "<reportId>"
    },
    "name": "get_report_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.
reportIdYesReport id from POST /api/v1/reports or GET /api/v1/reports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Comma-separated top-level fields to return, for example fields=id,stage. Omit to get everything. Spend fewer tokens by asking for less.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe read (readOnlyHint true, destructiveHint false), so the description's additional value is the auth requirement and the finished-report precondition, both of which matter operationally. It stops short of describing pagination or behavior when the report is not finished, but it clearly adds context beyond the annotations.

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?

Two compact clauses, front-loaded with the payoff (ranked moves) before the secondary question-tracking output and the access requirement. Dense parenthetical style costs a little readability but no sentence is wasted.

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?

With no output schema, the description carries the return-value burden and does so by naming the four fields in each move and the per-question winner rationale. It is nearly complete; only edge behavior (unfinished report, empty results) is undocumented.

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%, with reportId sourcing and the fields projection already documented in the schema. The description adds no syntax or constraint detail about either parameter, so baseline 3 applies.

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 names the resource (a finished report's actions) and enumerates the exact payload: up to three ranked moves with reason, exact edit, page and effort, plus per-question winner/loser detail. That distinguishes it from get_report and start_report, though the verb is implied rather than stated.

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?

'For a finished report' establishes the key precondition, and the required reports:read scope is stated. However, it never points to alternatives such as get_report for the report body or start_report for unfinished reports, so the agent must infer the routing itself.

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

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