Skip to main content
Glama

OpsRev Roofing AI

List SumoQuote project reports

sumoquote_list_reports
Read-only

List quote reports attached to a SumoQuote project UUID.

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": {
      "projectId": "<projectId>"
    },
    "name": "sumoquote_list_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
continuationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavior beyond that: it says nothing about pagination (even though a 'continuation' parameter exists), result ordering, or what a report record contains. For a read-only list tool with rich annotations the bar is lower, but this adds essentially nothing.

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 compact sentence with the resource and scope front-loaded and no filler. It is efficient, though its terseness is part of why other dimensions have gaps.

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

Completeness2/5

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

For a two-parameter tool with no output schema and zero schema description coverage, the description should at minimum explain the continuation cursor and what the returned reports represent. Neither is present, and there is no guidance on paging through a potentially large report list.

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

Parameters2/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 compensate and it only partially does. The UUID format for projectId is hinted at ('project UUID') and the schema enforces it with a regex, but the 'continuation' parameter is completely unexplained — the agent gets no hint that it is a pagination cursor or how to use it.

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?

States a specific verb ('List') and a specific resource ('quote reports attached to a SumoQuote project UUID'), so the agent knows exactly what it retrieves. However, it does not distinguish itself from the singular sibling 'sumoquote_get_report', so an agent must infer that this is the collection endpoint for a project's reports.

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: because projectId is required, the agent can infer this lists the reports belonging to one project. There is no explicit when-to-use versus 'sumoquote_get_report' or 'eagleview_list_reports', and no stated prerequisite (e.g., that the project must exist or that reports may be empty).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources