Skip to main content
Glama

OpsRev Roofing AI

Get an AccuLynx estimate

acculynx_get_estimate
Read-only

Read one estimate by its estimate ID.

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

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no not-found/error behavior, no note that a section or item listing is not included, no data-freshness context for an open-world external system.

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?

One sentence, zero waste, front-loaded with the verb and scoped to a single record. It is not padded, though its extreme brevity leaves the other dimensions under-served.

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?

With one parameter and rich read-only annotations, the surface area is small, so the description is close to sufficient. However, with no output schema and no statement of what a returned estimate contains (header only vs. sections/items), an agent cannot plan follow-up calls without guessing.

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 should carry the burden, but it only restates that the identifier is an estimate ID — which the parameter name estimateId already conveys. The regex pattern and 90-character limit live only in the schema, and the description clarifies neither the ID's origin nor whether it can be obtained from a job or list call.

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: 'Read one estimate by its estimate ID.' The singular 'one estimate' implicitly separates it from list-style siblings like acculynx_list_estimates, but it never names acculynx_get_estimate_section or acculynx_get_estimates to make the boundary explicit.

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 prerequisites, and no mention of alternatives. An agent must infer from the word 'one' that it needs a known ID rather than a job reference, and must guess whether sections/items require the separate sibling tools.

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