Skip to main content
Glama

Stratalize Intelligence

Get Intel Join

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

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond them: both result components (joint awards and the owner's general findings), a worked example with award count and dollar value, a cryptographic attestation/verification path, and a per-call price of $0.02 USDC. The cost and attestation details are the kind of thing an agent cannot infer from structured fields.

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?

Usage guidance is correctly front-loaded and the example is compact. However, the example sentence is visibly broken — "set against the district's 42 findings and." ends mid-clause — and the cryptographic-attestation/verify-URL pitch reads as promotional filler rather than operational guidance, costing the description its claim to tightness.

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 explaining returns, and it does identify both result components and gives a concrete-sized example, which is enough for an agent to know what to expect. It stops short of describing the fields or structure of the returned awards and findings, or whether results are paginated.

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%, so both required parameters (uei, owner) are already documented in the schema. The description clarifies that UEI identifies the contractor and that the pairing is contractor-under-owner, which reinforces but does not extend the schema's meaning. Baseline 3 applies when the schema does the heavy lifting.

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 awards where a contractor (identified by UEI) participated under a given owner, plus that owner's tribunal-decision findings as context. That is materially more precise than the name alone and implies this is a join of two resource types rather than a single-resource lookup. It falls short of a 5 only because it never names the single-resource siblings an agent might confuse it with.

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?

"Use when researching a contractor's track record with a specific owner before a bid or teaming decision" gives a concrete decision context for invoking the tool. It states when to use it clearly but offers no exclusions or explicit alternative tools when only one side of the join is needed.

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