Skip to main content
Glama

OpsRev Roofing AI

Create a SumoQuote project

sumoquote_create_project

Create a new SumoQuote quoting project for a homeowner and address. Confirm the details with the user before saving.

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": {
      "customerFirstName": "<customerFirstName>",
      "addressLine1": "<addressLine1>"
    },
    "name": "sumoquote_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
provinceNo
postalCodeNo
companyNameNo
phoneNumberNo
addressLine1Yes
addressLine2No
emailAddressNo
customerLastNameNo
customerFirstNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds a genuinely useful behavioral rule beyond the annotations — the human confirmation step before persisting. It says nothing about duplicate handling (non-idempotent creates can spawn duplicates), required permissions, or what is returned on success.

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 short sentences, front-loaded with the action and scope, with the confirmation rule as a natural follow-on. No filler or redundancy. It is efficient but so sparse that brevity shades into under-specification.

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 10-parameter create tool with 0% schema description coverage and no output schema, the definition leaves an agent without guidance on most inputs or on what a successful call returns. The confirmation instruction is a good start, but the description is not complete enough to drive a correct invocation without the agent guessing at field intent.

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% across 10 parameters, so the description carries the full burden of explaining them. It only gestures at 'homeowner and address', which vaguely maps to the name and address fields but never identifies the two required parameters (customerFirstName, addressLine1) or clarifies optional fields like companyName, phoneNumber, and emailAddress. With a low-coverage 10-param schema, this is a substantial shortfall.

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 and resource ('Create a new SumoQuote quoting project') and narrows scope to 'a homeowner and address', which tells an agent this is a create operation distinct from the get/list/search SumoQuote siblings. It stops short of explicitly naming any sibling or clarifying how it differs from the other create_* tools in the catalog, so it lands at 4 rather than 5.

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?

'Confirm the details with the user before saving' gives real procedural guidance about when to pause, which is more than a bare description. However, there is no statement of when this tool should be chosen over alternatives, no prerequisites (account/auth/plan requirements), and no exclusions such as what to do if the project already exists.

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