Skip to main content
Glama

get_intel_contractor_profile

Read-only

Use when vetting a contractor or bidder before a teaming decision or subcontract award. Returns the entity record plus award and bid participation history by role (winner, bidder, or vehicle holder). Example: Acme Paving LLC, winner on 14 of 61 bids (23% win rate), low bidder on 9 of those 14: a thin win margin worth checking against recent unit-price trends before teaming. Source: l. 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": {
      "contractor": "<contractor>"
    },
    "name": "get_intel_contractor_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
contractorYesUEI, legal name, or entity id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, open-world, so safety is covered. The description adds information annotations cannot carry: the data source, a cryptographic attestation with a verification URL, and a per-call cost of $0.02 USDC, all of which affect whether an agent should call it. It omits failure behavior when an entity is not found.

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?

Front-loads the trigger condition, then the return shape, then a worked example. The Acme Paving example earns its length by demonstrating how to read the win rate, but the attestation and payment sentences read as boilerplate appended to the body.

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 one-parameter read tool with no output schema, the description covers when to call, what comes back, where the data originates, and what it costs. It could say more about how incomplete or ambiguous entity matches are surfaced, which matters for a name-or-UEI lookup.

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?

There is a single required parameter and the schema describes it fully as a UEI, legal name, or entity id at 100% coverage. The description adds no disambiguation between those identifier forms, so the baseline of 3 applies.

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?

States a concrete verb and resource: it returns the entity record plus award and bid participation history, broken out by role (winner, bidder, vehicle holder). That is specific enough to separate it from a lettings search or an owner profile, though it never names the sibling it replaces.

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?

Gives an explicit triggering condition — vetting a contractor or bidder before a teaming decision or subcontract award. It stops short of stating when not to use it or which sibling tool to reach for when the question is about owners, lettings, or unit prices.

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