Skip to main content
Glama

BRAINIAC E-commerce Catalog Intelligence

Extract product attributes

ecommerce-catalog_product-attribute-extract

Read structured attribute pairs and lines labeled Attribute: name | value. Unlabeled description prose is not turned into a specification. Price $0.03 USDC. POST /api/v1/ecommerce-catalog/product-attribute-extract. Unpaid calls return 402 and do not run.

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": "ecommerce-catalog_product-attribute-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
productsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add genuinely useful behavior: cost ($0.03 USDC), payment gating (402 on unpaid calls, execution skipped), and a scoping rule (unlabeled prose is not converted). It omits whether results are returned, merged, or written back, and whether existing attributes are affected.

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?

Four short sentences, front-loaded with the input-format rule. The endpoint path and price sentences are boilerplate for a paid API but each carries operational meaning; little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a nested-schema, 4-input tool with no annotations and no output schema, so the description should explain input selection and what comes back. Instead it covers only price, transport, and one extraction rule, leaving the core invocation contract to inference.

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 coverage is 0% and the description mentions none of the four top-level parameters (csv, json, file, products). It never says inputs are mutually exclusive alternatives, never explains the nested product/attributes shape, and never clarifies precedence if several are supplied.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains which input text is treated as attributes ('Attribute: name | value' lines) and that unlabeled prose is excluded, which implies an extraction/parsing step. However, it never states the actual operation plainly (extract structured attribute pairs from supplied product data) and is mostly framed as a 'Read' with no object or outcome named.

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?

No when-to-use guidance is given, and no sibling is referenced. An agent has no way to know whether to call this versus ecommerce-catalog_product-normalize or ecommerce-catalog_product-variant-validate from this text alone.

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