Skip to main content
Glama

Agent Master Data

Search Agent Master Data

search_master_data
Read-onlyIdempotent

Paid x402 tool. Search trusted public master data for suppliers, locations, or organizations. Returns bounded golden-record summaries with match reasons, confidence, provenance, public-use status, freshness, and data-quality scores. Price ID: price.search.v1. Read masterdata://pricing before 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": {
      "query": "<query>"
    },
    "name": "search_master_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results per page.
queryYesFree-text search over golden records.
cursorNoOpaque pagination cursor from a previous response's meta.next_cursor.
entity_typeNoRestrict the search to one entity domain. Omitted means all v1 entity domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld=false), and the description adds real context beyond them: this is a paid x402 call, requires reading a pricing resource before payment, and returns a bounded result set with match reasons, confidence, provenance, public-use status, freshness, and quality scores. It stops short of describing failure modes or what happens when payment is not settled.

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 dense sentences, each carrying information (payment model, scope, return shape, prerequisite). The lead position is given to 'Paid x402 tool' rather than the core action, which is a minor front-loading miss but not wasteful.

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 enumerates the return fields and covers the payment precondition, so an agent knows what it will get and what it must do first. Pagination and error behavior are left to the schema and the pricing resource, which is acceptable for a 4-parameter read 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 description coverage is 100%, so query, limit, cursor, and entity_type are all documented in the schema itself. The description's mention of 'suppliers, locations, or organizations' merely restates the entity_type enum and adds no new format or constraint detail, 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 names a specific verb and resource ('Search trusted public master data for suppliers, locations, or organizations') and states what comes back (bounded golden-record summaries with match reasons, confidence, provenance). It does not explicitly contrast with close siblings like resolve_master_data_entity or get_master_data_golden_record, so it falls short of a 5.

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 gives one concrete prerequisite: read masterdata://pricing before payment, plus the price ID. However, it never says when to prefer this over resolve_master_data_entity or get_master_data_golden_record, so the agent must infer the boundary from the sibling names 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