Skip to main content
Glama

OpsRev Roofing AI

Search SumoQuote projects

sumoquote_search_projects
Read-only

List recent SumoQuote projects or search across all projects by customer name or address. Pass continuation from a prior response for the next page.

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": "sumoquote_search_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
continuationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 the safety profile is covered. The description adds genuinely useful behavior beyond that: that unfiltered calls return recent projects while filtered calls scan the full project set, and that results are paginated via continuation. It does not disclose page size, sort order, or result limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero filler, front-loading the two operating modes and then the pagination rule. Every clause carries information an agent needs.

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?

For a two-parameter, no-output-schema search tool, the definition covers both modes, both parameters, and pagination adequately. Minor gaps remain around result ordering, page size, and what a project record contains, but nothing prevents correct invocation.

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

Parameters4/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 both parameters, and it largely does: query is defined as a customer-name-or-address search, and continuation is defined as the next-page token taken from a prior response. The distinction that an absent query yields recent projects rather than nothing is also conveyed, though length constraints and edge cases are not.

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 names a specific verb pair and resource ("List recent SumoQuote projects or search across all projects") and states the searchable fields (customer name or address). It is clearly distinct from a single-project getter, though it does not explicitly name a sibling alternative.

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 implied: omit the query to get recent projects, supply a query to search all projects. The pagination instruction ("Pass continuation from a prior response") gives concrete when-to-use guidance for the second parameter, but there are no explicit exclusions or named alternatives.

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