Skip to main content
Glama

Find shops by name

em_shops
Read-onlyIdempotent

Search Emalls shops by partial name and return matching shop IDs, enabling you to retrieve detailed shop profiles.

Instructions

Search Emalls' list of shops by name and return their ids.

Use it when the user names a shop, to get its id for em_shop.

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

Input Schema

NameRequiredDescriptionDefault
pageNo48 shops per page.
queryYesPart of a shop name, e.g. دیجی.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • changedInput schema / properties / page / description
      Previous value: -"Page number, 48 shops per page."New value: +"48 shops per page."
    • changedInput schema / properties / query / description
      Previous value: -"Part of a shop name, e.g. دیجی or پرهان."New value: +"Part of a shop name, e.g. دیجی."
  2. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety bar is covered. The description adds value by disclosing the return shape (ids only, not full shop objects), which is important since there is no output schema; it does not mention result limits or paging behavior beyond what the schema states.

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?

Two short sentences with the capability first and the usage rule second, nothing redundant or padded.

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?

For a simple two-parameter lookup with full schema coverage and rich annotations, the description covers purpose, output type, and workflow. Only the boundary against em_search is left implicit.

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% — query is documented as a partial name with an example, and page documents 48 shops per page. The description adds no semantics beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ("Search Emalls' list of shops by name") plus what is returned ("return their ids"), which cleanly separates it from the sibling em_shop that fetches a single shop by id.

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?

Gives an explicit trigger ("when the user names a shop") and names the follow-on tool em_shop, so the agent knows the resolve-then-fetch workflow. It does not address how this differs from sibling em_search, which is the one plausible alternative left unaddressed.

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