Skip to main content
Glama

get_intel_lettings_search

Read-only

Use when scoping upcoming or recent construction lettings in a target geography before allocating bid and estimating resources. Returns bid tabulation line items filtered by owner, county, district, state, and letting date range. Example: Cook County, IL lettings in the last 90 days: 23 lettings, 340 bid items, concentrated in District 1 resurfacing work, a near-term bidding window w. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_intel_lettings_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
ownerNoOwner slug or id
stateNoTwo-letter state code, e.g. IL, TX
countyNo
date_toNoLetting date range end, YYYY-MM-DD
districtNo
date_fromNoLetting date range start, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds behavior the annotations do not carry: a per-call price of $0.02 USDC, cryptographic attestation, and a verification URL, all of which affect whether an agent should invoke it. The attestation and verification sentences read more like marketing than operational guidance, which caps the score below 5.

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 usage condition is correctly front-loaded, but the example sentence is bloated and visibly truncated ('a near-term bidding window w.'), which undermines trust in the text. The attestation and pricing tail adds value but is verbose, and the whole thing could be tightened without losing information.

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 seven optional parameters, no output schema, and an open-world scope, the description does enough: it says what comes back (bid tabulation line items) and the example sketches the return shape (letting counts, bid-item counts, district concentration). It leaves limit and result-cap behavior unexplained, which is the main remaining gap.

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 57%, so the description must carry some of the load. It does list the filterable dimensions (owner, county, district, state, letting date range), which maps to six of the seven parameters. However, it adds no meaning beyond the schema: county and district have no descriptions anywhere, and limit is never mentioned.

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 uses a specific verb and resource: it returns 'bid tabulation line items' for construction lettings, filtered by owner, county, district, state, and date range. That is concrete enough to separate it from sibling resources such as findings, contractor profiles, or unit prices. It stops short of naming a sibling to contrast against, which keeps it out of the top band.

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?

The opening clause gives a real usage context: scoping upcoming or recent lettings in a target geography before allocating bid and estimating resources. That is a clear when-to-use signal, not an implied one. It offers no when-not-to-use condition and points to no alternative tool when the agent needs a different resource.

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