Skip to main content
Glama
Sign In
Brandfetch MCP Server

Brandfetch MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Enrich a transaction descriptor

enrich_transaction
Read-onlyIdempotent

Resolve a transaction label and country into brand data via Brandfetch, so you can identify the merchant behind a descriptor. May consume credits; no charge or payment is made.

Instructions

Resolve the user-requested transaction label into brand data. Sends the label and country to Brandfetch and may consume credits; does not create a charge, bank connection or payment.

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": {
      "transaction_label": "<transaction_label>",
      "country_code": "<country_code>"
    },
    "name": "enrich_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoExact private profile label. Never inherits another profile or global key/client ID.
country_codeYesISO 3166-1 alpha-2 country code, uppercase.
transaction_labelYesOnly the specific transaction label requested by the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, but the description adds real value beyond them: it makes an outbound third-party call to Brandfetch, may consume credits, and explicitly denies charge/bank-connection/payment side effects. That is useful behavioral context for an agent.

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 tight sentences with zero filler. The core action comes first, followed by cost/side-effect information, so the most decision-relevant content is front-loaded.

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 3-parameter tool with no output schema and full schema coverage, the description covers the action, the external call, credit cost, and the absence of financial side effects. It could briefly indicate the shape of returned brand data, but nothing an agent needs to call it correctly is missing.

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 100%, so the parameters are already documented and the baseline is 3. The description only adds that the label and country are forwarded to Brandfetch; it says nothing extra about the account parameter or the country-code format.

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 (resolve/enrich) and resource (transaction label -> brand data), and clarifies it is not a payment or bank operation. It does not explicitly differentiate itself from the many sibling brand tools (get_brand, search_brands, prefetch_brand), so an agent must infer which to pick.

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?

The phrase 'user-requested transaction label' implies the trigger condition, and 'may consume credits' warns of cost. However, it never names alternatives such as get_brand or search_brands, nor says when not to use this tool, leaving routing to inference.

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