Skip to main content
Glama

Get product details

get_product
Read-onlyIdempotent

Return full details for one open-source product from the catalog: overview, feature groups, who it is for, what it replaces, and demo, source, and documentation links. Accepts a product slug such as openfront-gym or a plain name such as Gym.

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": {
      "product": "<product>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct slug (openfront-gym) or name (Gym).

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, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that results come from a bounded internal catalog and lists the returned sections, but says nothing about miss/error behavior or result size.

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?

Two tight sentences, front-loaded with the action and resource, followed by the payload contents and accepted input forms. No filler or repetition.

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, enumerating the returned fields is exactly the right compensation, and the single fully documented parameter needs little more. The only meaningful gap is undefined behavior for an unknown product name or slug.

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 schema already documents the single 'product' parameter with both example forms. The description's sentence about accepting a slug or plain name largely restates that, adding no new resolution rules or case-sensitivity details, so the baseline of 3 applies.

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 gives a specific verb and resource ('Return full details for one open-source product from the catalog') and enumerates the returned content (overview, feature groups, audience, replacements, links). It is clearly a single-product lookup, which implicitly contrasts with the search sibling, but it never names that alternative explicitly.

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 only implied: an agent can infer this is for fetching one known product. There is no explicit when-to-use statement, no guidance on choosing between this and search_software_alternatives, and no note on what happens when the product is unknown.

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