Skip to main content
Glama

OpsRev Roofing AI

List SumoQuote users

sumoquote_list_users
Read-only

List estimators and users on the connected SumoQuote account.

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_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
continuationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 structurally. The description adds only the account scoping and nothing about pagination, result caps, or whether membership/permissions are required, which is the remaining behavioral question for a list-users call.

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, so nothing is wasted. The brevity is efficient rather than padded, though it tips into under-specification given the undocumented parameter.

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?

The tool is structurally simple, but there is no output schema, and the description does not say what a user record contains or that results are paged via the continuation token. For a listing tool with an unexplained cursor parameter, that leaves an agent unable to call or consume it confidently.

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?

There is one parameter, "continuation", with 0% schema description coverage, and the description never mentions paging at all. With the schema providing no meaning, the description was the only place to explain that this string is a pagination cursor and it does not, leaving the sole parameter opaque.

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 ("List estimators and users") scoped to the connected SumoQuote account, which cleanly separates it from sibling tools like sumoquote_list_reports or sumoquote_search_projects. It stops short of a 5 because the distinction between "estimators" and "users" is never explained, so an agent cannot tell whether this returns two entity types or one.

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 guidance on when to call this tool, no prerequisites, and no mention of alternatives or the situation that selects them. The agent must infer that it is the lookup path for account people.

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