Skip to main content
Glama

OpsRev Roofing AI

List AccuLynx estimate items

acculynx_list_estimate_items
Read-only

List the items in one estimate section.

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>",
      "sectionId": "<sectionId>"
    },
    "name": "acculynx_list_estimate_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionIdYes
estimateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

The annotations already communicate read-only, non-destructive, open-world behavior. The description adds no further behavioral context such as pagination, ordering, response shape, or what happens with invalid or missing sections.

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?

The description is a single front-loaded sentence with no wasted wording. Structurally it is clean and immediately readable.

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 tool whose parameters are entirely undocumented in the schema and with no output schema, the description is too thin. It omits identifier semantics, pagination or ordering behavior, and any indication of what the returned items contain.

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%, so the description must carry the burden of explaining the two required parameters. It only implies an estimate and section relationship; it does not explain the identifier formats, constraints, or how estimateId and sectionId relate.

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 states a specific verb and resource: it lists items within one estimate section. This clearly identifies the operation, though it does not explicitly distinguish it from siblings such as get_estimate_section or list_estimate_sections.

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 use this tool versus get_estimate_section or list_estimate_sections. An agent must infer that it is for enumerating items inside a known section rather than retrieving section metadata.

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