Skip to main content
Glama

CPG Knowledge Graph

by io.github.greencore-solutions
OverviewDiscussionsAdmin

Find makers

find_makers
Read-onlyIdempotent

Global cross-node maker (supply) search. Filter by segment / region / node / has_website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoSovereign node code: the ISO 3166-1 alpha-2 code of the jurisdiction (e.g. FR, KR, AE), case-insensitive; list_nodes returns the 49 codes. Omit for all nodes.
limitNoMaximum rows to return, 1 to 500 (default 25).
regionNoRegion label as stored on the registry row (e.g. EU, ASIA), case-insensitive. Omit for all regions.
segmentNoMaker segment label as stored on the registry row (e.g. Haircare, Skincare); exact match. Omit for all segments.
has_websiteNotrue = only makers with a website on record; false = only makers without one; omit for both.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed5 schema fields changed
    • addedInput schema / properties / has_website / description
      Added value: +"true = only makers with a website on record; false = only makers without one; omit for both."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return, 1 to 500 (default 25)."
    • addedInput schema / properties / node / description
      Added value: +"Sovereign node code: the ISO 3166-1 alpha-2 code of the jurisdiction (e.g. FR, KR, AE), case-insensitive; list_nodes returns the 49 codes. Omit for all nodes."
    • addedInput schema / properties / region / description
      Added value: +"Region label as stored on the registry row (e.g. EU, ASIA), case-insensitive. Omit for all regions."
    • addedInput schema / properties / segment / description
      Added value: +"Maker segment label as stored on the registry row (e.g. Haircare, Skincare); exact match. Omit for all segments."
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the global scope and filterable dimensions but does not disclose additional behavior such as result ordering, default breadth when no filters are supplied, or any cross-node side effects; those are partially covered by the schema and output schema.

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?

The description is two short sentences with no filler: it states the global scope and then lists the available filters. All content is relevant and front-loaded.

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

Completeness5/5

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

All five parameters are optional and fully documented in the schema, the output schema exists, and annotations cover read/idempotent behavior. The description adds the necessary global cross-node context, making the tool complete enough for an agent to invoke correctly.

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%, and every parameter has a detailed description. The tool description only lists filter names that mirror the schema, adding no new semantic meaning beyond what the structured parameter descriptions already provide.

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 gives a specific verb and resource: 'Global cross-node maker (supply) search.' It clearly distinguishes this from sibling tools like find_retailers by identifying the resource as makers/supply butterfly and from node-scoped tools by emphasizing 'global cross-node.'

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?

The description establishes a clear context: use this tool for cross-node maker searches with filters. It does not explicitly name alternatives or provide when-not conditions, so it falls short of a 5, but the intended usage is immediately understandable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CPG Knowledge Graph toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources