Skip to main content
Glama
Sign In
Brandfetch MCP Server

Brandfetch MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Prefetch a brand

prefetch_brand
Destructive

Check if a brand identifier is indexed or enqueue a provider crawl via a confirmed HEAD request; returns 200 indexed or 202 crawl queued.

Instructions

Explicitly confirmed HEAD request can enqueue a provider crawl. Generic or domain route only. Return 200 indexed / 202 crawl queued; never poll, purchase or resubmit automatically.

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": {
      "identifier": "<identifier>"
    },
    "name": "prefetch_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoExact private profile label. Never inherits another profile or global key/client ID.
confirmNoSet true only when the user asked for exactly this action.
identifierYesDomain, email, URL, Brand ID, ticker, ISIN or crypto symbol. Explicit types accept only their identifier format.
identifier_typeNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.1
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for this exact provider crawl request."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false; the description adds real context beyond that by explaining the side effect (enqueuing a crawl), the return-code semantics (200 indexed / 202 crawl queued), and the no-auto-retry/no-purchase constraint. It stops short of describing cost or rate-limit implications that the 'purchase' reference hints at.

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?

Three dense sentences with no filler, front-loaded with the core effect and followed by routing scope, return codes, and constraints. It is compact, though the ordering of the mechanism before the action makes it slightly harder to parse on first read.

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?

With no output schema, the description usefully supplies the return-code meanings and the side-effect/constraint profile, which is exactly what an agent needs for this non-idempotent, potentially destructive call. The account/profile semantics are left entirely to the schema, but otherwise it is complete for a 4-parameter mutation-style tool.

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 75%, so most parameters are already documented in the schema. The description loosely maps 'Explicitly confirmed' to the confirm parameter and 'Generic or domain route only' to the identifier_type enum, but adds no format detail beyond what the schema already provides, so 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 states a concrete effect ('can enqueue a provider crawl') and the identifier scope ('Generic or domain route only'), so an agent can tell it triggers a crawl rather than reading data. It does not, however, name or differentiate from siblings such as get_brand or search_brands, and the 'HEAD request' framing is mechanism-oriented rather than action-oriented.

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?

It implies a prerequisite ('Explicitly confirmed') and lists things not to do ('never poll, purchase or resubmit automatically'), which is genuine usage guidance. But it never states when to prefer this tool over get_brand/search_brands, leaving the choice 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