Skip to main content
Glama

get_vendor_risk_signal

Read-only

Use when screening a vendor for financial instability or procurement risk before a long-term contract commitment. Returns a risk score from 0 to 1 with risk indicators and negative mention evidence. Example: Vendor X scores 0.72 risk — indicators: customer churn citations, pricing disputes, product roadmap uncertainty — HIGH risk classification, recommend short-term contract only. Source: Stratalize citation risk composite. $0.10 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": {
      "vendor_name": "<vendor_name>"
    },
    "name": "get_vendor_risk_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description does add genuinely useful context beyond them — the output shape (score plus indicators and evidence), the upstream source (Stratalize citation risk composite) and a per-call cost of $0.10 USDC, which is a real budgeting/rate-limit signal. It omits what happens on unknown vendors, whether a score of 1 means high or low risk direction explicitly tied to the scale, and latency/repeat-call caching behavior.

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?

The usage trigger is front-loaded, followed by output shape, worked example, source and price — a logical order with little filler. The example sentence is somewhat long relative to what it teaches, which keeps it from a 5.

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 does the necessary work by describing the score, the indicator/evidence payload and a classification example, so an agent knows what comes back. Gaps remain around vendor-not-found behavior and the mapping of score ranges to risk tiers, but the core contract is legible.

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?

There is one parameter with 0% schema description coverage, so the description must carry the meaning of vendor_name — but it only shows 'Vendor X' in an example. It does not say whether a legal entity name, ticker, domain, or DBA is expected, nor how ambiguous names are resolved, which is the main failure mode for a name-keyed lookup.

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 gives a specific verb and resource: screening a vendor for financial instability or procurement risk, and states the return artifact (0-1 risk score with indicators and negative mention evidence). It implicitly separates itself from sibling analytics tools by being vendor-specific and contract-timing scoped, but it never names an alternative such as get_vendor_benchmark or get_billing_coding_risk.

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 screening a vendor ... before a long-term contract commitment' supplies a clear triggering context rather than leaving usage implied. There is no explicit when-not condition and no named sibling routing, so it stops short of a full 5.

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