Skip to main content
Glama

Stratalize Intelligence

Get Intel Contractor Profile

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

A4/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, and non-destructive, so safety is not the burden here. The description adds real behavioral facts an agent cannot see elsewhere: a $0.02 USDC charge per call, a named source, and an attestation/verification path. The attestation and trust-url sentences read as promotional and are somewhat over-weighted, but the pricing disclosure is genuinely useful.

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?

It is correctly front-loaded with the trigger sentence and return shape. The example is long and carries interpretive commentary (thin win margin, check unit-price trends) that belongs in guidance rather than a call spec, and the attestation/verify block adds bulk that is not needed to invoke the tool.

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 must say what comes back, and it does: entity record plus award and bid history by role. The cost disclosure covers the main operational unknown. It does not address result completeness or how partial or ambiguous name matches are handled, which would matter for a lookup tool.

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% and the schema already says the single field accepts a UEI, legal name, or entity id, so the description adds little on that front. The worked example (Acme Paving LLC) does quietly confirm that a legal name is acceptable, which is a small but real addition over 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?

States a specific verb and resource plus scope: returns the entity record along with award and bid participation history broken out by role (winner, bidder, vehicle holder). That role breakdown distinguishes it from the plain owner-profile sibling without needing to open either schema.

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 concrete trigger: vetting a contractor or bidder before a teaming decision or subcontract award. What's missing is an explicit negative case or a named alternative for adjacent lookups, so the agent must infer which sibling to pick when it actually wants owner or unit-price data.

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