Skip to main content
Glama

Stratalize Intelligence

Get Vendor Onboarding Dossier

get_vendor_onboarding_dossier
Read-only

Use when onboarding a vendor or counterparty and you need one signed composite dossier for examiner-facing diligence. Fans in OFAC, OIG LEIE, and SAM exclusion screening (each with list_version), NPI provider verification, vendor market rate, and contract intelligence — degrading per-section when a sub-source is unavailable rather than failing the whole call. Input entity_name (required). $3.00 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": {
      "entity_name": "<entity_name>"
    },
    "name": "get_vendor_onboarding_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNo
stateNo
industryNo
entity_nameYes
entity_typeNo
company_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered; the description still earns credit by disclosing per-section degradation semantics ('rather than failing the whole call'), the presence of list_version per screening source, and a concrete $3.00 USDC per-call price. It does not explain what 'signed' entails, latency, or how degraded sections are flagged in the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the usage trigger, then capability scope, then the required input and price. Every clause carries information (sources, degradation behavior, cost) with no filler or restatement of the title.

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 composite tool with no output schema, the description usefully enumerates the sections the dossier returns and states the failure model and price, which is most of what an agent needs to call it correctly. The remaining gap is parameter guidance for the five optional inputs, which is a real deficiency for a six-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0% and six parameters, the description carries the full burden but only says 'Input entity_name (required)', which merely restates the schema's required field. The remaining five parameters (npi pattern, state length, industry, entity_type enum, company_size) get no meaning, so an agent cannot tell what entity_type or industry actually change about the dossier.

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 names a specific verb and resource ('one signed composite dossier') and enumerates exactly what it fans in: OFAC, OIG LEIE, SAM exclusion screening with list_version, NPI verification, market rate, and contract intelligence. This lets an agent distinguish it from single-source siblings like get_vendor_market_rate and get_vendor_contract_intelligence without opening a 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?

'Use when onboarding a vendor or counterparty and you need one signed composite dossier for examiner-facing diligence' gives a clear triggering context and audience. It stops short of explicit exclusions (e.g., 'for a single rate lookup use get_vendor_market_rate instead'), so the composite-vs-single-source routing is left to inference from the enumerated sections.

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