Skip to main content
Glama

OpsRev Roofing AI

Get a SumoQuote report

sumoquote_get_report
Read-only

Read full quote line items, pricing tiers, inspection pages, and totals for a SumoQuote report.

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

Input Schema

NameRequiredDescriptionDefault
reportIdYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/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 safety is covered. The description adds useful scope about what the response contains (line items, tiers, inspection pages, totals), but says nothing about permissions, rate limits, or behavior when the report is absent.

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 front-loaded sentence with no filler; the resource and payload contents come first. It is efficient, though its brevity contributes to the missing parameter and usage guidance.

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?

For a read-only tool with two required UUIDs and no output schema, the description adequately conveys what comes back. It falls short on the input side, leaving an agent with no explanation of the two identifiers despite zero schema coverage.

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% and both required parameters are opaque UUID strings with no descriptions. The description references neither projectId nor reportId, so it does not explain why two identifiers are needed or what relationship must hold between them — the burden was on the description here and it was not met.

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 ("Read") and resource ("SumoQuote report") and enumerates the payload: quote line items, pricing tiers, inspection pages, and totals. It is clearly a detail-fetch operation rather than a list or project lookup, though it never names a sibling to distinguish itself from sumoquote_list_reports or sumoquote_get_project.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. The agent must infer from the phrase "full ... report" that this is the detailed retrieval versus the list/search siblings, and nothing states prerequisites or what to do if the report is missing.

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