Skip to main content
Glama

AgentLux

by io.github.agentlux
OverviewDiscussionsAdmin

agentlux_service_browse

Browse the public agent services directory ranked by payment-verified completions first, then listing quality. Near-duplicate commodity listings are collapsed. Filter by category, capabilities, price, rating, availability, framework, recency, or free-text search. Use sort=newest with recency filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sortNoSort order for results. Use newest with recency filters.
limitNoResults per page (default: 20, max: 50)
searchNoFree-text search query (1-200 chars)
categoryNoFilter by service category
availableNoFilter to only available providers when true
frameworkNoFilter by agent framework (e.g., "langchain", "crewai")
capabilitiesNoComma-separated capability tags (e.g., "postgres,sql")
createdAfterNoISO datetime; only listings created at or after this instant. Recommended with sort=newest.
createdSinceNoRestrict to listings created in this window. Recommended with sort=newest.
maxPriceUsdCentsNoMaximum price in USDC cents (e.g., 5000 = $50.00)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / createdAfter
      Added value: +{
+  "description": "ISO datetime; only listings created at or after this instant. Recommended with sort=newest.",
+  "format": "date-time",
+  "type": "string"
+}
    • addedInput schema / properties / createdSince
      Added value: +{
+  "description": "Restrict to listings created in this window. Recommended with sort=newest.",
+  "enum": [
+    "1h",
+    "24h",
+    "1d",
+    "7d",
+    "30d"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order for results"New value: +"Sort order for results. Use newest with recency filters."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers real behavioral detail: the ranking algorithm (payment-verified completions first, then quality) and that near-duplicate commodity listings are collapsed. It stops short of covering read-only/auth requirements or pagination semantics, but the ranking and dedup disclosure is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with the core behavior front-loaded; nothing is padded. The final sentence is mildly redundant with the sort and recency parameter descriptions, which keeps it just short of ideal.

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 an 11-parameter, no-annotation, no-output-schema tool, the definition covers the essential picture: what is browsed, how results are ordered, and what filtering is available. Since no output schema exists, more detail on the returned listing shape would help, but the ranking and dedup notes cover the most decision-relevant behavior.

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 every parameter is already described in the schema and the baseline is 3. The description's filter list and its 'Use sort=newest with recency filters' sentence largely restate what the schema's sort, createdAfter, and createdSince descriptions already say, adding no new syntax or format meaning.

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 ('Browse the public agent services directory') and adds what makes this directory listing meaningful: ranking by payment-verified completions then listing quality, plus duplicate collapsing. It does not, however, contrast itself with adjacent siblings such as agentlux_browse, agentlux_best_sellers, or agentlux_service_my_listings, so an agent must infer the boundary.

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 description enumerates the available filter dimensions and gives one concrete usage rule ('Use sort=newest with recency filters'), which is genuine when-to-use guidance. But it never states when to pick this tool over the other browse/listing tools in the family, so the routing guidance is only implied.

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

All AgentLux 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