Skip to main content
Glama

Stratalize Intelligence

Get Intel Lettings Search

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.6/5.0
Behavior3/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 safety is covered. The description usefully adds commercial and access behavior that no annotation carries: $0.02 USDC per call and a signed settlement receipt with a verification URL. It stops short of the deeper traits an agent needs, such as pagination, default/maximum limit behavior, or what happens on empty results, and the post-quantum attestation sentence reads more promotional than operational.

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 use-case sentence and the filtered-returns sentence are well front-loaded. The example is helpful for output intuition but is verbose, and the closing trust/attestation sentence is marketing material that does not help an agent decide or call correctly. The description also ends mid-phrase ('a near-term bidding window w.'), which reads as a truncated artifact.

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 carries the burden of return-shape disclosure and does so via the example (lettings count, bid item count, district concentration). Pricing and verification context are present, and seven optional parameters are at least named. What remains missing is any statement of default result size or ordering, which matters for a tool with an unconstrained limit parameter.

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%: owner, state, date_from, and date_to are documented in the schema, while county, district, and limit are bare. The description enumerates owner, county, district, state, and letting date range, which partly compensates for the undocumented county and district fields, but it never states their accepted format (name vs. code vs. slug) and says nothing about limit. The worked example does convey what a filtered query yields, which is real added meaning.

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 definition states a specific verb and resource: it returns bid tabulation line items for construction lettings, filtered by owner, county, district, state, and letting date range. That is far more concrete than the title. It does not, however, explicitly contrast itself with close siblings such as get_intel_findings_search or get_intel_owner_profile, so an agent must infer the boundary.

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 genuine use case and decision point: scoping upcoming or recent lettings in a target geography before allocating bid and estimating resources. It supplies no exclusions, prerequisites, or named alternatives for when a different intel tool is the better fit, which keeps it short of a 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