Skip to main content
Glama

call_vendor

Call a vendor using the phone number in master data and ask a question, getting an immediate answer for accounts-payable verification tasks.

Instructions

Phone the vendor on the number in the master data and ask a question. The answer comes back immediately.

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>",
      "question": "<question>"
    },
    "name": "call_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes
vendor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two useful facts — the action is a real phone call to a third party, and the response is synchronous ("comes back immediately") — but says nothing about cost, call recording, what happens on no-answer or voicemail, or whether the call is logged against the vendor record.

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?

Two sentences, no filler, and the core action is front-loaded. The second sentence is short but earns its place by conveying synchronous return behavior that the schema cannot express.

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 tool with no annotations and no output schema, the description should say more about what the agent receives back — a transcript, a summarized answer, or raw speech — and how failures surface. "The answer comes back immediately" is directionally useful but underspecified for a side-effecting external action.

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 description coverage is 0%, so the description must compensate for both parameters. It partially does: vendor_id is explained as resolving to a phone number held in master data, and question is implied by "ask a question." However, it adds nothing about question format, length, phrasing, or what a valid vendor_id looks like.

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?

States a specific verb and resource — "Phone the vendor" — plus the payload (a question) and the resolution source (the number in master data). This clearly distinguishes it from data-reading siblings like get_vendor or search_vendors, though it never names an alternative explicitly.

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 or when-not-to-use guidance, no prerequisites, and no routing to alternatives such as send_email or get_vendor. The only hint of usage is the implicit 'ask a question' framing, which leaves the agent to infer that this is for outbound vendor inquiries rather than data retrieval.

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