Skip to main content
Glama

Moqway

Get supplier profile

get_supplier
Read-onlyIdempotent

Supplier verification and Moqway's rating over the last 365 days: an overall 0–100 score and eight dimensions (fulfilment against the factory's own promised ship time, order reliability, product quality, match to listing, packaging, after-sales, repeat buyers, verification). Each dimension has its sample size, confidence and raw metrics, plus a plain-English summary, strengths and watch-outs. Suppliers with fewer than 3 paid orders are labelled 'new'. The breakdown needs a connected buyer account.

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": {
      "supplier_id": "<supplier_id>"
    },
    "name": "get_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
supplier_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish it is a read-only, idempotent, non-destructive, non-open-world call, so safety needs no restating. The description adds real context beyond that: the 365-day evaluation window, the 'new' labelling rule for suppliers with fewer than 3 paid orders, the eight scoring dimensions, and the dependency on a connected buyer account. It does not explain what happens when the account is not connected (error vs empty breakdown), which keeps it short of a 5.

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 core deliverable, the score and its eight dimensions, is front-loaded, and the qualifiers (new-supplier threshold, buyer-account requirement) are consolidated at the end. Every sentence conveys distinct information about the return payload, with no filler or repetition.

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 must describe the return shape, and it does so thoroughly: aggregate score, per-dimension sample size, confidence, raw metrics, narrative summary, strengths and watch-outs. The single notable gap is the missing supplier_id guidance and the unspecified failure mode when no buyer account is connected.

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?

There is one parameter, supplier_id, with 0% schema description coverage, so the description carries the burden of explaining it. It only indirectly hints at the entity ('the factory's own promised ship time', 'Suppliers with fewer than 3 paid orders') without saying where the id comes from, its expected format, or whether it is a platform supplier id versus an external factory id. The rich score explanation is about the output, not the input, so this is borderline minimum-viable.

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 resource (supplier verification plus Moqway rating) and spells out exactly what the payload contains: an overall 0–100 score, eight named dimensions with sample size/confidence/raw metrics, summary, strengths and watch-outs. The verb is implicit in the name/title rather than the body, and no sibling is named, but none of the listed siblings (orders, products, disputes) could be confused with it.

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 only implied: an agent can infer it fetches a supplier's trust/quality profile using a supplier_id. The one genuine usage constraint given is that the detailed breakdown requires a connected buyer account, which is useful, but there is no statement of when to call this versus e.g. get_product or search_products, and no exclusion cases.

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