Skip to main content
Glama
Sign In

discovery

by dev.nexbid
OverviewDiscussionsAdmin

nexbid_product

Read-onlyIdempotent

<tool_description> Get detailed product information by ID from the Nexbid marketplace. Returns full product details including price, availability, description, and purchase link. </tool_description>

<when_to_use> When you have a specific product UUID from a previous nexbid_search result. Do NOT use for browsing — use nexbid_search instead. </when_to_use>

<combination_hints> Typically called after nexbid_search to get full details on a specific product. If user wants to buy → follow with nexbid_purchase. </combination_hints>

<output_format> Full product details: name, description, price, currency, availability, brand, category, purchase link. </output_format>

Input Schema

NameRequiredDescriptionDefault
agent_idNoAgent identifier for analytics-attribution.
product_idYesProduct UUID
session_idNoSession token for multi-turn correlation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "Agent identifier for analytics-attribution.",
+  "maxLength": 64,
+  "type": "string"
+}
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Session token for multi-turn correlation.",
+  "maxLength": 64,
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, establishing a safe, non-mutating operation. The description adds useful behavioral context by enumerating the returned information (price, availability, description, purchase link) and noting it is 'full product details.' No contradictions with annotations.

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?

The description is organized into short, purposeful sections (description, when_to_use, combination_hints, output_format). Every sentence adds value; there is no redundancy or filler.

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

Completeness5/5

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

For a simple read-only tool with one required parameter and three well-documented parameters, the description fully covers purpose, usage, output format, and workflow context. Even without an output schema, the output_format section lists the expected fields. Rich annotations and combination hints complete the picture.

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 description coverage is 100%, so the schema already documents all three parameters. The description adds meaning beyond the schema by explaining that product_id comes from a previous nexbid_search result, which clarifies the parameter's origin and intended use.

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 the tool's action: 'Get detailed product information by ID from the Nexbid marketplace.' It specifies the resource (Nexbid product), scope (by ID), and explicitly distinguishes itself from browsing via nexbid_search and purchasing via nexbid_purchase.

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

Usage Guidelines5/5

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

Provides explicit when-to-use: 'When you have a specific product UUID from a previous nexbid_search result.' Also gives a clear exclusion: 'Do NOT use for browsing — use nexbid_search instead.' Addition of combination hints reinforces workflow (search → product → purchase).

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

All discovery toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources