Skip to main content
Glama
Sign In

Kifly — Agentic Commerce & Payments

by ai.kifly
OverviewDiscussionsAdmin

list_sellers

Read-onlyIdempotent

List all active sellers on the Kifly network. Requires a network token (kfn_live_…). Returns each seller's handle, name, city, region, delivery coverage (nationwide:true or a states list), delivery fee, and catalog size. delivery_coverage.cities may be capped to a handful of entries — compare cities.length against city_count; if fewer, call get_seller for that seller's full city list. Use this to discover which sellers are available and which ship to a buyer's location before calling get_seller or search_products. Pagination: when kifly:hasMore is true, pass kifly:nextCursor as cursor to fetch the next page. Default page size is 20, max 50.

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_sellers"
  }
}

Input Schema

NameRequiredDescriptionDefault
metaNo
limitNoMax sellers per page (default 20, max 50).
cursorNoPagination cursor from kifly:nextCursor in a previous response. Omit on the first call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / meta / description
      Removed value: -"Who is calling. See kifly://docs/mcp."
    • changedInput schema / properties / meta / properties / ucp-agent / properties / profile / description
      Previous value: -"https:// URL of your agent's UCP profile. No API key needed."New value: +"Your agent's UCP profile URL. No key needed."
  2. Changed2 schema fields changed
    • changedInput schema / properties / meta / description
      Previous value: -"Who is calling (canonical UCP `meta`). See kifly://docs/mcp."New value: +"Who is calling. See kifly://docs/mcp."
    • changedInput schema / properties / meta / properties / ucp-agent / properties / profile / description
      Previous value: -"https:// URL of the UCP profile your agent publishes. Send it, need no API key."New value: +"https:// URL of your agent's UCP profile. No API key needed."
  3. Changed3 schema fields changed
    • changedInput schema / properties / meta / description
      Previous value: -"Canonical UCP `meta` envelope. Send `ucp-agent.profile` to call Kifly with no credential at all; omit it entirely when authenticating with a Bearer key."New value: +"Who is calling (canonical UCP `meta`). See kifly://docs/mcp."
    • removedInput schema / properties / meta / properties / ucp-agent / description
      Removed value: -"Who is calling. The profile is required but not verified."
    • changedInput schema / properties / meta / properties / ucp-agent / properties / profile / description
      Previous value: -"Absolute https:// URL of the UCP profile YOUR agent publishes about itself. Send this and no Kifly API key is required for supported tools."New value: +"https:// URL of the UCP profile your agent publishes. Send it, need no API key."
  4. Changed1 schema field changed
    • addedInput schema / properties / meta
      Added value: +{
+  "additionalProperties": true,
+  "description": "Canonical UCP `meta` envelope. Send `ucp-agent.profile` to call Kifly with no credential at all; omit it entirely when authenticating with a Bearer key.",
+  "properties": {
+    "ucp-agent": {
+      "additionalProperties": false,
+      "description": "Who is calling. The profile is required but not verified.",
+      "properties": {
+        "profile": {
+          "description": "Absolute https:// URL of the UCP profile YOUR agent publishes about itself. Send this and no Kifly API key is required for supported tools.",
+          "format": "uri",
+          "maxLength": 512,
+          "type": "string"
+        }
+      },
+      "required": [
+        "profile"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "ucp-agent"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: it discloses the network-token auth requirement, the exact response shape, a data-truncation quirk (capped delivery_coverage.cities) with the field comparison needed to detect it, and full pagination mechanics (hasMore/nextCursor).

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?

Four sentences, each carrying distinct load: scope, auth, return shape, escalation rule, pagination. The escalation caveat is placed before the usage sentence so the agent reads it before deciding to chain calls.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 correctly carries the return-value burden by listing response fields and the coverage-shape distinction (nationwide flag vs states list). Auth, pagination limits, and the downstream tool path are all present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description reinforces limit semantics (default 20, max 50) and explains the cursor round-trip via kifly:hasMore/kifly:nextCursor, which the schema only states statically. The gap is the meta.ucp-agent.profile parameter, which appears nowhere in the description — the "network token" sentence refers to auth, not the profile URL field.

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?

Opens with a specific verb and resource ("List all active sellers on the Kifly network") and immediately enumerates the returned fields, making the scope unambiguous. It is clearly distinguishable from siblings like get_seller and search_products, which the description names as later-stage tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit use case ("discover which sellers are available and which ship to a buyer's location") and states the ordering relative to get_seller and search_products. It also names a concrete when-to-escalate condition: if cities.length < city_count, call get_seller for the full list.

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

All Kifly — Agentic Commerce & Payments toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources