Skip to main content
Glama
Sign In
cloudcostwise

cloudcostwise

by cloudwise-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_findings

Read-onlyIdempotent

Lists findings from the last scan with IDs, optionally filtered by waste type or minimum monthly savings in USD to help prioritize cost-saving reviews.

Instructions

List findings from the last scan, with ids, optionally filtered by waste type or a minimum monthly saving in USD.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_findings"
  }
}

Input Schema

NameRequiredDescriptionDefault
waste_typeNo
min_monthly_savingsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.18

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world behavior, so the safety profile is covered. The description adds the useful scope constraint that results come from the last scan only, but says nothing about result limits, pagination, or what happens when no scan has run.

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?

A single sentence that front-loads the action and scope, then appends the filters. No filler, though the phrase 'with ids' is slightly awkward and the filter clause is dense.

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

Completeness3/5

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

An output schema exists, so return shape needn't be described, and the tool has only two optional parameters. Still missing are the accepted waste_type values and edge-case behavior (no prior scan, default savings threshold), which matter for correct invocation.

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 0%, so the description must carry the parameter burden; it does clarify that waste_type filters by waste type and min_monthly_savings is a floor in USD, which the bare schema does not. However, it never lists valid waste_type values or explains that min_monthly_savings defaults to 0, leaving the vocabulary unknown.

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 gives a specific verb and resource ('List findings'), scopes it ('from the last scan'), notes what comes back ('with ids'), and enumerates the two filters. It is clear enough to separate from siblings like explain_finding and fix_guidance, though it never names them explicitly.

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?

Usage is only implied: an agent can infer this is the enumeration entry point and that explain_finding/fix_guidance handle follow-up detail, but the description never states when to pick this tool over a fresh 'scan'. No exclusions or prerequisites are given.

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

Deploy Server

Other Tools