Skip to main content
Glama

Get Product

get-product
Read-only

Get full public details of one Noonlaunch product by its slug (the last part of its noonlaunch.com/product/... URL).

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
slugNoThe product slug, e.g. "my-product" for noonlaunch.com/product/my-product.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds that only 'full public' details are returned, which usefully bounds the data surface, but says nothing about behavior for a missing/invalid slug or return shape.

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?

A single sentence with no waste, and the resource and lookup key are front-loaded. Every clause ('one product', 'by its slug', URL hint) earns its place.

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?

For a one-parameter read tool with full schema coverage, complete annotations, and no output schema, the description is sufficient to invoke it correctly. The only minor gap is the absence of any note on retrieval failure behavior.

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% and the slug parameter is documented with an example in the schema itself, so the schema carries the load. The description's parenthetical ('last part of its noonlaunch.com/product/... URL') reinforces the same meaning rather than adding new constraints.

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?

States a specific verb and resource ('Get full public details of one Noonlaunch product') and scopes it to a single item by slug. It is clearly distinguishable from list-launch-directories or search-directory, though it doesn't explicitly contrast with its closest sibling, check-product.

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

Usage Guidelines3/5

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

Usage is implied by 'one product by its slug' and 'public details', but there is no explicit when-to-use, when-not, or pointer to an alternative such as check-product. An agent can infer the context but must reason about it.

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.