Skip to main content
Glama

OpsRev Roofing AI

List AccuLynx estimate sections

acculynx_list_estimate_sections
Read-only

List sections on one estimate.

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": {
      "estimateId": "<estimateId>"
    },
    "name": "acculynx_list_estimate_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
estimateIdYes

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 structurally. The description adds essentially nothing beyond that — no note on pagination, ordering, whether an empty estimate yields an empty list, or error behavior for an invalid estimateId. The only added nuance is that the listing is scoped to one estimate.

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 zero padding; the key scope qualifier comes first. It is efficient, though its brevity edges into under-specification rather than tightness.

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 simple read-only list tool with a single required parameter and annotations covering the safety profile, this is roughly the minimum viable definition. With no output schema, the description could still say what a section represents or how results are ordered, which it omits.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter at 0% schema description coverage, so the description must carry meaning. "On one estimate" confirms estimateId identifies the parent estimate, but adds no format, sourcing, or lookup guidance (e.g., where to obtain the ID), and the schema's pattern/length constraints are left unexplained.

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?

"List sections on one estimate" gives a specific verb (list) and resource (sections) with explicit scope (a single estimate), which cleanly separates it from the singular get_estimate_section and from list_estimate_items. It stops short of naming any sibling, so the differentiation is inferred rather than stated.

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 when-to-use guidance, no mention of prerequisites such as needing a valid estimate ID, and no routing to alternatives like get_estimate or get_estimate_section. The agent must guess the context from the name alone.

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