Skip to main content
Glama
Sign In
rangeview-mcp

rangeview-mcp

by IamMichael23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get product detail

get_product

Retrieve complete product details including description, attributes, brand, stock, rating, and image by providing a product ID, slug, or SKU.

Instructions

Full detail for one product by id, slug, or SKU: description, attributes (caliber, barrel length, action…), brand, stock, rating and image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoNumeric product id
skuNoStore SKU
slugNoURL slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 full burden. It describes the return fields but does not mention behavior on missing products, authorization, or side effects. For a read-only tool, this is adequate but could be improved.

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?

Single sentence that is front-loaded with the main purpose, followed by a list of return fields. No unnecessary words.

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 lists the returned information (description, attributes, brand, stock, rating, image). It lacks mention of error handling or that only one identifier should be provided, but covers the essentials.

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%, but the description adds value by explaining that id, slug, or SKU are alternative identifiers for the product, which is not explicit in 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?

The description clearly states it provides full detail for a product by id, slug, or SKU, listing specific fields. It distinguishes from sibling tools like search_products which return lists.

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?

It specifies how to identify the product (by id, slug, or SKU), implying the agent should use exactly one. While it doesn't explicitly state when not to use this tool, the context of sibling tools makes it clear this is for single product detail.

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