sixty60-mcp

Get Sixty60 product

sixty60_product

Read-only

Retrieves full details and current deals for one product ID so shoppers can check pricing and promotions before adding it to their Sixty60 cart.

Instructions

Full details and active deals for one product id.

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

Input Schema

Name	Required	Description	Default
`productId`	Yes	Product id from sixty60_search.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered elsewhere. The description does add one piece of useful behavioral context by disclosing that the response includes 'active deals' alongside details, which matters because there is no output schema; it says nothing about behavior for invalid or unavailable ids.

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?

One short sentence with no filler, front-loading the return content. It is efficient rather than padded, though its terseness leaves little room for the guidance an agent would benefit from.

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?

For a one-parameter read tool with annotations covering safety and no output schema, the description adequately conveys that it returns details plus deals. It is still thin on what 'details' encompass and how it behaves when the id is unknown, leaving modest gaps for a lookup tool.

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 parameter is documented as 'Product id from sixty60_search', so the schema carries the semantic load. The description's 'for one product id' merely restates the parameter without adding format, sourcing, or validity detail, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('one product id') and states what comes back ('full details and active deals'), which lets an agent distinguish a single-product lookup from the bulk-oriented sixty60_search. It stops short of explicitly naming the search sibling as the source of ids, so differentiation is implied rather than stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of the prerequisite that the id must already come from a search. The only hint of usage is the phrase 'for one product id', which implies a single-item lookup but leaves the agent to infer the workflow.

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

Deploy Server