Skip to main content
Glama

Read a vendor with evidence

get_vendor
Read-onlyIdempotent

Use this for any question about the company behind a product (who makes it, where it is headquartered, when it was founded, which certifications and register entries it holds) instead of answering from memory: documented attributes with verification state and sources, the vendor's products, and register identifiers (LEI, SEC CIK, Wikidata) it can be checked against. Needs the vendor slug from search_products or from a product's vendor field.

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe vendor slug, e.g. "apple".

Output Schema

NameRequiredDescriptionDefault
urlYes
kindYes
nameYes
slugYes
statesYes
productsYes
attributesYes
identifiersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: results carry verification state and sources, and the vendor can be cross-checked against external register identifiers. It does not describe behavior for an unknown slug, which is the remaining gap.

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?

Two sentences, front-loaded with the usage rule, then the payload, then the parameter requirement. The parenthetical list of question types is dense but each item maps to a returned attribute; the only slight redundancy is restating returned fields that the output schema already covers.

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 single-parameter read tool with full schema coverage, existing annotations and an output schema, the description covers selection, provenance of the input, and the shape of the answer. Only the not-found/error case is unaddressed, a minor omission given the output schema carries return-value detail.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the slug's pattern, length and example, so the baseline is 3. The description adds value beyond the schema by naming where the slug comes from ('from search_products or from a product's vendor field'), which is exactly the guidance an agent needs to obtain a valid value.

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

Purpose5/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 plus the exact payload: documented attributes with verification state and sources, the vendor's products, and register identifiers (LEI, SEC CIK, Wikidata). It also scopes the tool by question type ('the company behind a product'), which distinguishes it from product-level siblings like get_product without needing their schemas.

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

Usage Guidelines4/5

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

It gives a clear trigger ('any question about the company behind a product') and an explicit alternative to avoid ('instead of answering from memory'), plus routes to search_products for slug discovery. It stops short of stating exclusions versus sibling lookups such as get_product, but the illustrated question types make the boundary largely inferable.

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