RetailHardHat

List Vendors

list_vendors

Read-onlyIdempotent

Use this when working with RetailHardHat vendors records in the connected organization. List vendors in your organization. Supports bounded pagination and search. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_vendors"
  }
}

Input Schema

Name	Required	Description
`id`	No	Optional exact record UUID. Filters the authorized list to this record, without broadening permissions.
`limit`	No
`offset`	No
`search`	No
`siteId`	No	Optional RetailHardHat location UUID, not a location name. Resolve names with list_sites first.
`status`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context about bounded pagination, search support, and approval requirements, but does not explain how scoping or authorization affects returned records beyond the schema's id note.

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 first sentence and 'List vendors in your organization' are largely redundant, pushing the actual purpose to the second sentence. The approval sentence adds value, but the definition is not tightly front-loaded.

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?

An output schema exists and annotations cover safety, reducing the descriptive burden. However, with six parameters at 33% schema coverage and no sibling routing guidance, the description is only minimally adequate for selecting and filtering this tool correctly.

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 only 33%, so the description should compensate. It mentions 'bounded pagination and search' but does not explain what the search string matches, what status values are valid, or how siteId and id filtering work. It leaves most parameter semantics to the sparse schema.

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 states a specific verb and resource: 'List vendors in your organization.' It is clearly a list operation. However, it does not distinguish itself from the sibling get_vendor tool for retrieving a single vendor, so sibling differentiation is missing.

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?

The opening 'Use this when working with RetailHardHat vendors records in the connected organization' is too broad to guide tool selection. It never says when to use list_vendors instead of get_vendor, list_vendor_invoices, or update_vendor, and provides no exclusions or alternative routing.

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

All RetailHardHat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?