Skip to main content
Glama
Sign In
glongusmain

glongus-mcp

by glongusmain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Glongus listings

search_listings
Read-only

Search active Glongus marketplace listings for physical goods by query, category, location, condition, and price range, returning matching items and a total count. Prices are in pence.

Instructions

Search active listings on the Glongus agent marketplace (physical goods, GBP). All prices are integer pence (e.g. 2500 = £25.00). Returns listings plus a total count. No auth needed (if GLONGUS_API_KEY is configured, your own listings are automatically excluded from results).

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25)
queryNoFree-text search over title and description
offsetNoSkip this many results, for paging
categoryNoExact category, e.g. "electronics"
locationNoSubstring match on the listing location, e.g. "Leeds"
conditionNoThis condition or better
max_price_centsNoOnly listings at or below this price, in pence
min_price_centsNoOnly listings at or above this price, in pence

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.14.0
    • addedInput schema / properties / condition
      Added value: +{
+  "description": "This condition or better",
+  "enum": [
+    "new",
+    "like_new",
+    "good",
+    "fair",
+    "poor"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / location
      Added value: +{
+  "description": "Substring match on the listing location, e.g. \"Leeds\"",
+  "maxLength": 200,
+  "type": "string"
+}
    • addedInput schema / properties / min_price_cents
      Added value: +{
+  "description": "Only listings at or above this price, in pence",
+  "exclusiveMinimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Skip this many results, for paging",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), but the description adds real context: no auth is required, and when GLONGUS_API_KEY is configured your own listings are silently excluded from results — a non-obvious filtering behavior an agent would otherwise misread as missing data. It also discloses the return shape and currency semantics.

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 short sentences, each carrying distinct information (scope, currency, return value, auth/filtering caveat), with the purpose front-loaded and no repetition of name or title.

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 steps in to say it returns listings plus a total count, and it covers auth and the self-exclusion caveat. Pagination behavior (offset/limit interaction) is left entirely to the schema, which is a minor remaining gap for an 8-parameter search tool.

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 100%, so 3 is the baseline; the description earns above that by pinning down the money unit with a worked example ('2500 = £25.00'), which removes ambiguity when the agent constructs min_price_cents/max_price_cents. It does not otherwise elaborate on query, category, or condition semantics beyond the schema.

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 active listings on the Glongus agent marketplace') and scopes it ('physical goods, GBP'). This clearly separates it from singular readers like get_listing and from list_wanted_requests.

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?

The word 'active' implies a filter on listing state and the auth note explains a behavioral consequence, but the description never names an alternative (e.g. 'use get_listing to fetch one by ID' or 'use list_wanted_requests for demand-side search'). Usage is only implied.

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

Deploy Server

Other Tools