Skip to main content
Glama

Get Physical Product Overview

get_physical_product_overview
Read-only

Get overview data for a managed physical product. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "productId": "<productId>"
    },
    "name": "get_physical_product_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYesProduct ID, from a Nas.com product listing for this business.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / productId / description
      Added value: +"Product ID, from a Nas.com product listing for this business."
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real access-control context: business-plan gating, a mandatory permission check, and required grace-period/resubscribe messaging before proceeding. It stops short of describing what the returned overview contains, which matters given there is no output schema.

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?

Purpose is front-loaded in the first sentence, followed by the permission sequence in a logical order. The gating instructions are dense but each clause is actionable; slightly more text is spent on access procedure than on the tool's own behavior.

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?

Access/permission behavior is thoroughly covered, but with no output schema the definition should indicate what the "overview" actually returns so an agent knows what it will get back. That gap, plus no differentiation from sibling product-read tools, leaves it only adequate overall.

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%, with productId and communityId both documented in-schema including the "never invent one" caveat. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

"Get overview data for a managed physical product" states a verb and resource, but "overview data" is essentially the title restated and leaves unclear what fields or summary this returns versus siblings like get_physical_product or get_physical_product_analytics. An agent cannot tell from the text alone which of these product-read tools to pick.

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?

Gives explicit preconditions and a hard exclusion: call check_business_tool_access before collecting inputs, and FREE businesses can never use this tool regardless of feature rows. It does not name an alternative product-read tool for cases where this one is inappropriate, so it stops short of full when/when-not/alternatives coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources