Skip to main content
Glama

Product details

get_product
Read-onlyIdempotent

Details of one Klarframe product: what it is, how the rollout works, example scenarios, integrations, privacy and FAQ. Klarframe publishes no prices.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: de, en, es or it. Defaults to de.de
slugYesProduct slug, e.g. inbound-voice

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description discloses the shape of the returned content and a real business constraint (Klarframe publishes no prices), which prevents a wasted expectation. It does not mention lookup failure behavior for an invalid slug, which keeps it from a 5.

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 sentences, zero filler. The resource is stated first and the surprising constraint (no prices) is placed as a short trailing note where it is easy to retain.

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?

There is no output schema, so the description carries the burden of describing returns, and the enumerated content areas do that job well. What remains unstated is minor: whether the whole record is always returned or sections can be absent.

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 both parameters carry enums with descriptions, so the description correctly leaves slug and lang to the schema. It adds no meaning beyond that, which is the expected baseline here.

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?

"Details of one Klarframe product" gives a specific resource and singular scope, which implicitly separates it from the sibling list_products. It then enumerates the content areas returned (rollout, scenarios, integrations, privacy, FAQ), so the agent knows exactly what it gets. It stops short of naming the sibling alternative explicitly, keeping it at 4.

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: fetch this when you need depth on a single product. There is no explicit when-to-use vs list_products or search_content, though "no prices" usefully preempts a query category the agent might otherwise attempt. Adequate but with a clear guidance gap.

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