Skip to main content
Glama

Search sub-merchants

search_merchants
Read-onlyIdempotent

Search, by name, the sub-merchants the signed-in user can act as.

Returns up to 50 matches, each with its merchant_id and name. It is the search behind the jobmojito_configuration picker's Search button; list_my_merchants (its search) returns the same accounts as text.

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": "search_merchants"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoPart of a sub-merchant's name, case ignored; empty lists the first 50.
llm_modelNoYour model id, e.g. "claude-opus-4-8"; "unknown" if unsure. For analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
resultYes
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / description
      Added value: +"Part of a sub-merchant's name, case ignored; empty lists the first 50."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a real behavioral fact beyond them — results are capped at 50 matches, each carrying merchant_id and name — but says nothing about authorization requirements for acting as a merchant or what happens beyond the cap.

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?

Front-loaded with the core action, then the result shape, then the routing context. Every sentence carries information, though the jobmojito_configuration picker reference is UI-specific detail that a calling agent may not need.

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 an output schema present, the description needn't explain return values, and annotations cover the safety profile; params are fully described in schema. What remains thin is disambiguation from list_sub_merchants, the closest-named sibling, which the description ignores entirely.

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 all three parameters are already fully documented, including the empty-string-lists-first-50 behavior. The description's 'by name' phrasing restates the query parameter rather than adding matching rules, ranking, or partial-match behavior beyond what the schema states.

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 and resource with scope: search sub-merchants 'by name' that the 'signed-in user can act as'. It explicitly distinguishes itself from the sibling list_my_merchants by noting that one returns the same accounts as text, though the other obvious sibling list_sub_merchants is never addressed.

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?

Usage is clear in context: this is the search behind the jobmojito_configuration picker's Search button, and list_my_merchants is named as the text-listing alternative. There is no explicit 'use this instead of X when...' statement, so the choice is inferred rather than stated.

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.