Skip to main content
Glama
Sign In
Payables MCP

Payables MCP

by zeybekci-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_vendor

Retrieve a single vendor record by its vendor ID to support accounts payable workflows such as bill processing and vendor validation.

Instructions

Fetch one vendor by id.

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_idYesVendor id, e.g. V-01

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and does almost nothing with it. It does not say what happens when the vendor id does not exist, whether soft-deleted vendors are returned, what permissions are required, or what shape the response takes — all of which matter for a lookup tool.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but its terseness is under-specification rather than disciplined brevity. It is appropriately short, not notably well-structured.

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 trivial one-parameter read with no output schema and a fully documented parameter, the description is minimally sufficient to invoke the tool. Given the absence of annotations, though, an agent gets no signal about failure modes or auth, leaving it only barely adequate.

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 coverage is 100% and the sole parameter is documented with an example format ('V-01'), so the schema does the heavy lifting. The description adds no syntax, format, or validation detail beyond what the schema already provides, which is the baseline case.

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 (Fetch) and resource (vendor) and constrains it to a single record by id. No sibling tool fetches a vendor, so sibling collision is not a real risk here, but the description never references any sibling to anchor its place in the workflow.

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, no mention of prerequisites, and no pointer to any alternative such as a search or list tool. The agent must infer that this is the single-record lookup path rather than a query path.

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

Deploy Server

Other Tools