Skip to main content
Glama

get_intel_owner_profile

Read-only

Use when assessing a construction owner's claims history before bidding a contract or negotiating a change order. Returns aggregate finding counts by defect family and outcome, decisions in the corpus, and days and dollars claimed versus awarded. Example: USACE Norfolk District, 42 findings, 31% denial rate on notice-and-time-bar defenses, $22M claimed versus $9M awarded: a hard line. 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": {
      "owner": "<owner>"
    },
    "name": "get_intel_owner_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesOwner slug or id, e.g. illinois-dot

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, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: the return contents, cryptographic attestation, a verification URL, and a per-call cost of $0.02 USDC.

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?

The description is front-loaded with the use case and return contents, then adds an illustrative example, attestation details, verification URL, and cost. It is generally efficient, though the example and attestation language make it slightly longer than strictly necessary.

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

Completeness5/5

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

For a one-parameter, read-only profile tool with no output schema, the description explains when to use it, what it returns, how results are attested, where to verify, and the cost. Nothing essential for correct invocation appears to be missing.

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 100%, and the single owner parameter is already documented with a slug/id example. The description does not add syntax or format details beyond the schema, so the baseline of 3 is appropriate.

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 states a specific resource and output: a construction owner's claims-history profile with aggregate finding counts, decisions, and claimed-versus-awarded dollars. It is clear what the tool does, but it does not explicitly distinguish itself from sibling profile tools such as get_intel_contractor_profile or get_party_litigation_profile.

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?

It gives a clear usage context: assessing an owner's claims history before bidding a contract or negotiating a change order. It does not state when not to use the tool or name alternative tools for adjacent owner/contractor/litigation questions.

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