Skip to main content
Glama

Get vendor

get_vendor

One company across every ecosystem Lode covers: its stable vendor id, domains, and its integration on each platform (for example Stripe on Xero and on Vercel). Look up by vendor id, domain, or name.

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": {
      "query": "<query>"
    },
    "name": "get_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesVendor id ("stripe"), domain ("stripe.com") or name ("Stripe")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full disclosure burden. It usefully explains that the result spans ecosystems and includes each platform's integration, but says nothing about behavior when a vendor is not found, whether a domain lookup can return multiple vendors, or any rate/permission constraints.

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, zero filler, with the identity of the resource front-loaded before the lookup keys. The 'Stripe on Xero and on Vercel' example earns its place by making the cross-ecosystem scope concrete.

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?

For a one-parameter read tool with no output schema, the description does the important work of describing what the response contains (vendor id, domains, per-platform integrations). The only meaningful gap is not-found/ambiguity behavior, which is minor for this complexity level.

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 single 'query' parameter already documents the three accepted forms with examples. The description's sentence merely restates those same three forms, adding no new syntax or disambiguation value; the baseline 3 applies.

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 names a concrete resource ('One company across every ecosystem Lode covers') and enumerates what it returns: stable vendor id, domains, and per-platform integration. It implicitly separates this aggregate view from the per-platform get_integration tool, but never names a sibling, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

'Look up by vendor id, domain, or name' establishes the access pattern but gives no when-to-use vs when-not guidance and never contrasts this with find_integrations, get_integration, or compare_integrations. Usage is implied rather than stated.

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