Skip to main content
Glama

get_vendor

Retrieves a vendor's master record—contact details, bank account, and payment terms—by vendor ID so accounts-payable agents can verify payee information before processing invoices.

Instructions

Vendor master record: contact on file, bank account on file, payment terms.

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_id": "<vendor_id>"
    },
    "name": "get_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and largely drops it: it never states this is a read-only lookup, that it returns nothing on an unknown id, or that the bank account data is sensitive. Its one real contribution is disclosing the returned fields (contact, bank account, payment terms), which partially substitutes for the absent output schema.

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?

It is a single tight fragment with no filler, and the returned-field list is front-loaded. Brevity is appropriate, though the telegraphic style leaves it short of a complete statement of intent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 this is nearly adequate: the field list gives an agent a rough idea of the payload despite no output schema. It is still missing anything on id format, not-found behavior, and read-only semantics, which matters given zero annotation coverage.

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% and vendor_id is completely undocumented — no format, no source, no indication whether it is the internal id or an external vendor number. The description adds nothing about the parameter, so an agent must guess what to pass.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Vendor master record') and enumerates what it contains, so an agent can infer it fetches a single vendor's details. But it uses a noun phrase with no verb, and it does not distinguish itself from siblings like search_vendors or call_vendor, leaving the read-a-vendor-by-id purpose implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all — nothing says to use this when you already have a vendor_id versus search_vendors when you only have a name, and nothing rules out update_vendor_bank or call_vendor. The only hint is the required vendor_id in the schema, which is structural, not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.