Skip to main content
Glama

List hangel Market stores

list_stores
Read-onlyIdempotent

List partner stores on hangel Market with their donation rate (the approximate share of each purchase that reaches the NGOs the buyer chose, after hangel's share and taxes are taken from the commission the brand pays), highest first.

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

Input Schema

NameRequiredDescriptionDefault
sortNo"donationRate": highest first (default); "name": alphabetical.donationRate
limitNoMaximum number of results in this page (default 50, at most 200).
queryNoStore name or category. Turkish or English, or German, Spanish, French, Arabic, Russian, Persian, Azerbaijani, Hungarian, Hausa or Danish.
cursorNonextCursor from the previous call of this tool, to get the next page. Other arguments can be omitted; if given, they must match that call.

Output Schema

NameRequiredDescriptionDefault
asOfNoTime the statuses and dates were evaluated (ISO 8601).
sortYesSort order used.
queryNoPresent when a query was given.
totalYesNumber of matching records (all pages).
offsetYesPosition of the first record of this page in the full result.
storesYes
hasMoreYestrue when more records follow; call again with nextCursor.
returnedYesNumber of records in this page.
nextCursorYesOpaque cursor for the next page, or null on the last page.
donationModelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "nextCursor from the previous call of this tool, to get the next page. Other arguments can be omitted; if given, they must match that call.",
      +  "maxLength": 2000,
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results (default 50, at most 200)."New value: +"Maximum number of results in this page (default 50, at most 200)."
    • changedInput schema / properties / query / description
      Previous value: -"Store name or category. Turkish or English."New value: +"Store name or category. Turkish or English, or German, Spanish, French, Arabic, Russian, Persian, Azerbaijani, Hungarian, Hausa or Danish."
    • addedInput schema / properties / sort
      Added value: +{
      +  "default": "donationRate",
      +  "description": "\"donationRate\": highest first (default); \"name\": alphabetical.",
      +  "enum": [
      +    "donationRate",
      +    "name"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "asOf": {
      +      "description": "Time the statuses and dates were evaluated (ISO 8601).",
      +      "type": "string"
      +    },
      +    "donationModel": {
      +      "type": "string"
      +    },
      +    "hasMore": {
      +      "description": "true when more records follow; call again with nextCursor.",
      +      "type": "boolean"
      +    },
      +    "nextCursor": {
      +      "description": "Opaque cursor for the next page, or null on the last page.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "offset": {
      +      "description": "Position of the first record of this page in the full result.",
      +      "type": "integer"
      +    },
      +    "query": {
      +      "description": "Present when a query was given.",
      +      "properties": {
      +        "expansion": {
      +          "description": "Query terms that were matched across languages through the hangel multilingual dictionary, and the forms searched in the content.",
      +          "items": {
      +            "properties": {
      +              "concepts": {
      +                "items": {
      +                  "type": "string"
      +                },
      +                "type": "array"
      +              },
      +              "searchedAs": {
      +                "items": {
      +                  "type": "string"
      +                },
      +                "type": "array"
      +              },
      +              "term": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "term",
      +              "concepts",
      +              "searchedAs"
      +            ],
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "normalized": {
      +          "description": "The query after case, accent and punctuation normalisation (the raw query is not echoed).",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "normalized",
      +        "expansion"
      +      ],
      +      "type": "object"
      +    },
      +    "returned": {
      +      "description": "Number of records in this page.",
      +      "type": "integer"
      +    },
      +    "sort": {
      +      "description": "Sort order used.",
      +      "type": "string"
      +    },
      +    "stores": {
      +      "items": {
      +        "properties": {
      +          "category": {
      +            "type": "string"
      +          },
      +          "contentLanguage": {
      +            "description": "BCP 47 code of the language the text fields are written in, as stored on hangel (for example \"tr\" or \"en\"); \"und\" when it cannot be determined. Texts are not machine-translated unless \"translated\" is true.",
      +            "type": "string"
      +          },
      +          "donationRate": {
      +            "description": "Approximate share of a purchase that reaches the NGOs, in percent, after hangel's share and taxes are taken from the commission the brand pays; 0 for stores of social enterprises or NGOs.",
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "ownerOrg": {
      +            "description": "Present for stores of a social enterprise or NGO (no donation rate).",
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Public page of the record on hangel.org.",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "slug",
      +          "name",
      +          "donationRate",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "Number of matching records (all pages).",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "offset",
      +    "returned",
      +    "hasMore",
      +    "nextCursor",
      +    "sort",
      +    "stores",
      +    "donationModel"
      +  ],
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"En çok sonuç sayısı (varsayılan 50)."New value: +"Maximum number of results (default 50, at most 200)."
    • changedInput schema / properties / query / description
      Previous value: -"Mağaza adı ya da kategori."New value: +"Store name or category. Turkish or English."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds genuine domain context by defining what the donation rate actually measures (share reaching NGOs after hangel's cut and taxes on the brand's commission), which an agent cannot derive from structured fields.

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?

A single front-loaded sentence with no filler; the long parenthetical is dense but every clause carries real information about the ranking metric.

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 complete schema descriptions, full annotations, and an output schema handling return values, the description only needs to convey purpose and the ranking metric, which it does. Minor gap: it never mentions pagination or the cursor workflow, though the schema covers it.

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 coverage is 100%, so all four parameters (sort, limit, query, cursor) are already documented in detail, including enum values and pagination semantics. The description only restates the default 'highest first' ordering, adding nothing beyond the schema — 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?

States a specific verb and resource ('List partner stores on hangel Market') and names the key attribute returned (donation rate). It does not explicitly distinguish itself from sibling discovery tools like 'search' or 'search_products', so it stops 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?

Usage is implied: browse/discover partner stores ranked by donation rate. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as 'search' when the user has a specific query in mind; that guidance is left to inference.

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