Skip to main content
Glama

AgentMart

by ai.ciphyr.agentmart
OverviewDiscussionsAdmin

Search the catalog

search_catalog
Read-only

Search the shelves. Each item shows its price, the estimated cost to build it yourself, test results and verified agent reviews.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoThe same as query (the REST name); query wins when both are given.
queryNoWhat you need, in a few words. Matches whole words.
shelfNoutility: always-on services; kit: tested code to download; human: work by AgentMart's own team.
passport_tokenNoNot needed on this public tool; accepted and ignored.
max_price_centsNoOnly items at or below this price, in US cents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / q
      Added value: +{
+  "description": "The same as query (the REST name); query wins when both are given.",
+  "maxLength": 200,
+  "type": "string"
+}
    • changedInput schema / properties / shelf / description
      Previous value: -"utility: always-on services; kit: tested code to download."New value: +"utility: always-on services; kit: tested code to download; human: work by AgentMart's own team."
    • changedInput schema / properties / shelf / enum
      Previous value: -[
-  "utility",
-  "kit"
-]New value: +[
+  "utility",
+  "kit",
+  "human"
+]
  2. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / max_price_cents / description
      Added value: +"Only items at or below this price, in US cents."
    • addedInput schema / properties / passport_token
      Added value: +{
+  "description": "Not needed on this public tool; accepted and ignored.",
+  "maxLength": 200,
+  "type": "string"
+}
    • addedInput schema / properties / query / description
      Added value: +"What you need, in a few words. Matches whole words."
    • addedInput schema / properties / shelf / description
      Added value: +"utility: always-on services; kit: tested code to download."
  3. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description usefully adds that each returned item carries price, build-cost estimate, test results, and verified agent reviews. Since no output schema exists, this disclosure of return content is meaningful added value. It stops short of noting pagination or result limits.

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?

Two short sentences with zero filler, and the core action ('Search the shelves') is front-loaded before the payoff description. Nothing could be cut without losing information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter search tool with no output schema, the description partially compensates by listing what results contain, which is the most useful missing piece. However, it omits result limits, ordering, and pagination behavior, leaving the return contract incomplete.

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 description coverage is 100% and each parameter is well documented in the schema, so the baseline is 3. The description only indirectly touches parameters ('price' hints at max_price_cents, 'shelves' hints at the shelf enum) without adding syntax or matching behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Search the shelves,' which conveys a catalog search over items but leans on the domain metaphor ('shelves') and never states what is being searched. It does not distinguish this tool from catalog-adjacent siblings such as get_item or list_utilities, so an agent must infer the boundary. Purpose is understandable but not sharply defined.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like get_item (fetch a known item) or list_utilities (browse a category). No prerequisites, no indication of what querying is appropriate for. The description offers only a one-line hint at result content, not usage context.

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

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