Skip to main content
Glama

OpsRev Roofing AI

Get an AccuLynx estimate section

acculynx_get_estimate_section
Read-only

Read one section on an 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>",
      "sectionId": "<sectionId>"
    },
    "name": "acculynx_get_estimate_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionIdYes
estimateIdYes

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, openWorldHint=true and destructiveHint=false, so the safety profile is covered externally. The description adds nothing beyond that: it does not say what a section contains, whether items roll up into totals, what happens when the sectionId does not belong to the estimate, or what a missing section returns.

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 wasted words and no ambiguity in phrasing. It is terse, but the terseness is not padding — the gap is missing content rather than excess content.

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?

No output schema exists and the parameters are undocumented, so the description is the only place to explain what a returned section looks like. For a read tool whose whole value is the returned shape, one sentence states the target but not the payload, leaving the agent without enough context to use the result.

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 for both parameters and does not. It implies that sectionId identifies a section within estimateId, but gives no format, no note that both are required, and no constraint that the section must belong to the given estimate — the only available meaning is inferred, not stated.

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 (Read) and resource (one section on an estimate), which is clearer than a bare title restatement. It does not distinguish itself from the sibling list_estimate_sections or acculynx_get_estimate, so an agent must infer that this returns a single section rather than a collection.

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?

No when-to-use guidance, no prerequisites, and no mention of the sibling alternatives for listing sections or fetching the whole estimate. The agent is left to guess whether to call this or acculynx_list_estimate_sections.

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