Skip to main content
Glama

get_intel_join

Read-only

Use when researching a contractor's track record with a specific owner before a bid or teaming decision. Returns awards where that contractor (by UEI) participated under that owner plus the owner's general tribunal-decision findings for context. Example: USACE Norfolk District and a mid-Atlantic marine contractor, 6 joint awards worth $84M, set against the district's 42 findings and. 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>",
      "uei": "<uei>"
    },
    "name": "get_intel_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
ueiYesContractor UEI
ownerYesOwner slug or id

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 cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely new behavioral facts: a per-call price of $0.02 USDC, a cryptographically attested post-quantum signed receipt, and a verification endpoint. It does not state rate limits, latency, or whether the two result sets (awards and findings) arrive in a single payload, which keeps it short of a 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 trigger is well front-loaded, but the illustrative sentence is truncated mid-clause ('set against the district's 42 findings and.'), which reads as a generation defect rather than usable content. The payment/attestation tail is relevant but sits awkwardly after the broken example.

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?

For a two-parameter, read-only lookup with no output schema, the description covers the research question, the two result components, a worked example, cost, and verification. What remains unspecified is result shape (per-award fields, currency normalization, whether findings are summarized or full text), which matters for downstream use.

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 100% for both required parameters, so the baseline is 3. The description reinforces that UEI identifies the contractor and that owner is an owner slug/id, and the USACE Norfolk District example illustrates a valid owner value, but it adds no format, casing, or resolution rules beyond the schema.

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?

The description states a specific verb and a precisely scoped resource: awards where a named contractor (by UEI) participated under a named owner, plus that owner's tribunal-decision findings. The relational scope ('contractor under that owner') inherently separates it from the contractor-profile and findings-search siblings without needing to name them.

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 triggering situation: 'Use when researching a contractor's track record with a specific owner before a bid or teaming decision.' That is concrete guidance, but it names no alternative tool or exclusion condition, so an agent cannot tell from this text when to prefer get_intel_contractor_profile or get_intel_findings_search instead.

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