Costory: Your Finops MCP

get_report_execution

Read-only

Get a condensed execution summary: status, destination, per-widget summaries, URLs. Use when the user asks about one specific report run or delivery. Omits raw time-series and full DIGEST trees. Widgets with drillDown can be expanded via get_report_execution_widget (pass returnImage there for a stored GRAPH_SNAPSHOT PNG). For DIGEST, tell the user tree and node investigations are available. EXAMPLE: { executionId: "clx…" }

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": {
      "executionId": "<executionId>",
      "context": "<context>"
    },
    "name": "get_report_execution"
  }
}

Input Schema

Name	Required	Description
`slug`	No	Organization slug. Omit to auto-detect from your account (fails if you belong to multiple orgs).
`context`	Yes	A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
`llm_model`	No	The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
`executionId`	Yes	Report execution id.
`conversation_id`	No	The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 14, 2026

changedInput schema / properties / context / description

Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details."

changedInput schema / required

Previous value: -[
-  "executionId",
-  "context",
-  "llm_model"
-]New value: +[
+  "executionId",
+  "context"
+]

Changed4 schema fields changedNov 12, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "executionId"
-]New value: +[
+  "executionId",
+  "context",
+  "llm_model"
+]

First observedAug 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: it is a lossy/condensed view (time-series and full DIGEST trees stripped out), and the GRAPH_SNAPSHOT image must be fetched elsewhere, which prevents an agent from expecting pixels or raw series here. It stops short of stating error behavior for an unknown executionId.

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 the capability, then scope, then alternatives, then an example — a sensible reading order with no filler. It is dense (one long first sentence) and the DIGEST instruction is slightly tangential to invoking the tool, but every clause conveys routing or content 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?

With no output schema, the description carries the burden of describing returns, and it does: status, destination, per-widget summaries, URLs, plus explicit exclusions. The five analytics/context parameters are self-documented in the schema. Remaining gap is minor: no guidance on failure modes (invalid or missing executionId) or the shape of per-widget summaries.

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 every parameter carries its own description, so the schema already does the heavy lifting. The description only repeats executionId in an inline example ({ executionId: "clx…" }), which confirms the cuid shape the pattern already encodes but adds no new meaning for slug, context, llm_model or conversation_id. Baseline 3 applies.

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?

States a specific verb and resource ('Get a condensed execution summary') and enumerates the contents: status, destination, per-widget summaries, URLs. It also draws its own boundary by naming what is omitted (raw time-series, full DIGEST trees), so an agent can separate it from get_report_execution_widget and the DIGEST/tree tools 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?

Explicitly scopes use to 'when the user asks about one specific report run or delivery' — a single-run lookup, not a listing. It names the follow-up alternative for drillDown widgets (get_report_execution_widget, with the returnImage note for GRAPH_SNAPSHOT) and directs the agent to surface tree/node investigation for DIGEST, so the sibling routing is stated rather than inferred.

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

All Costory: Your Finops MCP tools Inspect

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

Need Help?