Skip to main content
Glama

Get a product at every store

get_network_product

Retrieves the same product across multiple stores on the Monity Network, returning each store's tracker, latest value and availability so you can compare prices and stock.

Instructions

The same product tracked at different stores on Monity Network ("available at 2 of 3 stores", cheapest): each store's tracker, its latest value and availability. Only stores confirmed by a product code or by the trackers' owners. Give the product id from a change record's thing.id (query_network_records) or the slug of any of its trackers. Not found when fewer than two stores are public.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ref": "<ref>"
    },
    "name": "get_network_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesA change record's thing.id, or a tracker's slug or id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful behavior: inclusion is limited to stores confirmed by product code or by tracker owners, the response ranks by cheapest, and the two-public-store threshold acts as a failure mode. It says nothing about authentication, rate limits, or whether results are cached/live, so the safety and access profile is incomplete for a no-annotation tool.

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?

Front-loads the core concept and then tacks on scoping, identifier sourcing, and the not-found rule, each earning its place. The sentence structure is fragmentary (parenthetical example, comma-spliced clauses), which makes it dense but not padded.

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 and no annotations, the description still explains return content (per-store tracker, latest value, availability, cheapest, X-of-Y count) and the identifier input, which covers what an agent needs to call it. Missing only access/permission context and whether the value data is real-time.

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% and the single param's schema text already enumerates "thing.id, or a tracker's slug or id," which the description largely restates. The only added value is pointing at query_network_records as the source of thing.id, so the baseline 3 fits.

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 resource and operation: the same product aggregated across stores on the Monity Network, with concrete output shape ("available at 2 of 3 stores", cheapest) and per-store tracker/value/availability. An agent can distinguish this from get_tracker (single tracker) and query_network_records (change records) without opening any schema.

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?

Tells the agent exactly which identifier to supply and where it comes from: a change record's thing.id via query_network_records, or a tracker's slug. It also gives a failure precondition ("not found when fewer than two stores are public"). It stops short of naming an alternative for single-store lookups or stating when not to use this tool at all.

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