Skip to main content
Glama

get_intel_unit_prices

Read-only

Use when benchmarking a bid line-item price against recent public lettings before finalizing an estimate. Returns minimum, maximum, average, and sample count unit prices for a pay item code, filterable by owner, state, and county. Example: pay item 20101100 (clearing and grubbing) in Texas, average $2,340 per acre across 46 bid items, range $1,180 to $4,900: a wide spread that flags. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

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": {
      "pay_item_code": "<pay_item_code>"
    },
    "name": "get_intel_unit_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNoOwner slug or id
stateNoTwo-letter state code, e.g. IL, TX
countyNo
pay_item_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely non-schema behavior: the aggregate return shape, a metered cost of $0.02 USDC per call, and cryptographic attestation with a verification URL. These are material facts an agent would not otherwise know, though the 'flags' interpretation hint is left unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded and earn their place. The example is useful but the trailing fragment 'a wide spread that flags' is dangling, and the attestation/verify/pricing tail reads as promotional boilerplate, albeit carrying the one useful fact of per-call cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly takes on the burden of describing return values (min, max, average, sample count), which it does. Cost and trust signals round it out. The main gap is that two of four parameters, including the required pay_item_code format and county, are left undocumented.

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 coverage is 50%: owner and state have descriptions, county and pay_item_code do not. The description partially compensates by restating that results are filterable by owner, state, and county and by giving a concrete pay item example (20101100 in Texas), but it never explains the county filter's format or how owner slug vs. id resolves. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('benchmarking a bid line-item price'), names the exact aggregation returned (min, max, average, sample count unit prices for a pay item code), and scopes it to public lettings data. An agent can distinguish this from sibling tools like get_intel_lettings_search (which finds lettings) or get_intel_owner_profile without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear when-to-use framing: 'Use when benchmarking a bid line-item price against recent public lettings before finalizing an estimate,' which ties it to a concrete decision point. It does not name alternatives or state when-not to use it (e.g., when you need raw individual bid items rather than an aggregate), which keeps it below 5.

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