Skip to main content
Glama

OpsRev Roofing AI

Get AccuLynx job estimates

acculynx_get_estimates
Read-only

Find estimate records for one known AccuLynx job.

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": {
      "jobId": "<jobId>"
    },
    "name": "acculynx_get_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 and the bar is lower. The description contributes the scoping fact that results are bound to a single job, but says nothing about result ordering, pagination, or what an empty result means for a plural 'estimates' endpoint.

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?

A single front-loaded sentence with no filler; the scoping constraint appears immediately rather than being buried after boilerplate.

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?

This is a low-complexity read-only tool with one required parameter and no output schema, so the description needn't explain return fields. Still, it leaves ambiguous whether multiple estimate records are returned, how they are ordered, and what happens when the job has no estimates.

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?

Schema description coverage is 0%, so the only parameter, jobId, is documented solely by its type, length and pattern constraints. The description adds a small amount of meaning by indicating it must be a known AccuLynx job identifier, but it does not explain the ID format or where the caller obtains one.

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 gives a specific verb ('Find') and resource ('estimate records') and narrows the scope to 'one known AccuLynx job', which separates it from a broad listing tool such as acculynx_list_estimates. It stops short of naming that sibling explicitly, so an agent must infer the boundary from the phrase 'one known job'.

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?

'For one known AccuLynx job' implicitly states the prerequisite that the caller must already have a job identifier, which is useful context for choosing this tool over a search or list tool. However, there is no explicit when-to-use/when-not-to-use guidance and no named alternative for discovering estimates without a known job.

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