Skip to main content
Glama

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.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered — and the description adds genuinely new behavioral facts: partial-failure semantics ('degrading per-section when a sub-source is unavailable rather than failing the whole call'), per-section list_version provenance, a signed output artifact, and a $3.00 USDC per-call price. Those are the exact traits an agent needs before invoking a metered, multi-source aggregation. Nothing here contradicts the annotations.

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?

The single paragraph is front-loaded with the triggering scenario, then the component inventory, then degradation behavior, then the required input, then price — a sensible information order with no filler sentences. Every clause (list_version, signed, degrading, $3.00) contributes a fact an agent could act on. Density is high but not padded.

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 convey what comes back, and it does reasonably well: a signed composite dossier with per-section results, list versions, and graceful degradation instead of total failure. The remaining hole is input-side — five of six parameters are undocumented anywhere — which matters for a paid call where a bad entity_type or missing npi wastes the $3.00.

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?

Schema description coverage is 0% across 6 parameters, so the description carries the full explanatory burden — yet it only restates 'Input entity_name (required)', which the schema already marks required. Five parameters go entirely unexplained: npi (10-digit pattern), state (2-char), industry, company_size, and especially entity_type with its individual/entity/vessel/aircraft enum, which materially changes screening behavior. No guidance on which optional fields improve match quality or when to supply them.

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 deliverable — 'one signed composite dossier for examiner-facing diligence' — and enumerates exactly what is fanned in: OFAC, OIG LEIE, SAM exclusion screening, NPI provider verification, vendor market rate, and contract intelligence. That enumeration implicitly distinguishes it from the single-source siblings (e.g. get_vendor_market_rate, get_vendor_contract_intelligence) by making clear this is the bundled call. An agent can identify the tool's job without opening the 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 scenario, which is stronger than most definitions. It stops short of explicit when-not guidance — there is no statement telling the agent to call an individual sibling (e.g. the standalone market-rate or contract-intelligence tools) when only one component is needed. The cost line implies a tradeoff but does not spell out the alternative path.

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