Skip to main content
Glama

MarketAIVerse

by com.marketaiverse
OverviewDiscussionsAdmin

What changed since you were last here

whats_new

The shelf keeps a log of what changed - things added, things removed, and things whose price, state, licence or evidence label moved. Send the marker we gave you last time and you get only what you have not seen; send nothing and you get the whole log. Wording changes are deliberately not tracked, because a log full of reworded sentences stops being read. If nothing changed you get an empty list and a marker to send next time, which means you can stop reading and come back later instead of walking the whole catalogue again. Needs no identity. Read-only, and needs nothing. An empty answer means nothing changed, which is a real answer rather than a failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoThe marker from your last call (`$next_time_send`), as unix seconds or an ISO date. Leave it out for everything we have.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / since / description
      Previous value: -"The marker from your last call (`$data_viitoare_trimite`), as unix seconds or an ISO date. Leave it out for everything we have."New value: +"The marker from your last call (`$next_time_send`), as unix seconds or an ISO date. Leave it out for everything we have."
  2. Changed2 schema fields changed
    • removedInput schema / properties / dupa
      Removed value: -{
-  "description": "The marker from your last call (`$data_viitoare_trimite`), as unix seconds or an ISO date. Leave it out for everything we have.",
-  "type": "string"
-}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "The marker from your last call (`$data_viitoare_trimite`), as unix seconds or an ISO date. Leave it out for everything we have.",
+  "type": "string"
+}
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses read-only behavior, no identity requirement, the deliberate exclusion of wording changes, and the important semantic that an empty result means 'nothing changed' rather than failure.

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?

The description is somewhat long but every sentence adds meaningful information. It is front-loaded with the core purpose and then covers behavior, exclusions, and empty-result semantics. Minor redundancy exists in 'Needs no identity. Read-only, and needs nothing.' but it does not detract significantly.

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?

The description is nearly complete for a single-parameter tool with no output schema. It explains what is tracked, how to use the marker, and what an empty result means. A slight gap is that it only explicitly mentions receiving a marker in the empty case, leaving the non-empty response marker slightly implied rather than stated.

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?

The schema already covers the single `since` parameter well, so the baseline is 3. The description adds value by explaining the behavioral consequence of omitting it versus sending it, and clarifies that the marker comes from a previous call (`$next_time_send`).

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?

The description clearly identifies the tool as a change log for the shelf, listing the exact kinds of tracked changes (added, removed, price/state/licence/evidence label moved). It also distinguishes itself from full-catalogue browsing by noting this is an incremental alternative to walking the whole catalogue again.

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

Usage Guidelines4/5

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

The description explains the two usage modes: send the previous marker to get unseen changes, or send nothing to get the entire log. It also implies the tool is for return visits rather than initial exploration, though it does not name sibling tools or give explicit when-not-to-use guidance.

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

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