Skip to main content
Glama
Sign In
torob-mcp

torob-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Product URL

tb_product_url
Read-onlyIdempotent

Converts a product ID or Torob link into a clean, standardized product URL without making a network request.

Instructions

Clean torob.com URL for a product id, path or link (no request is sent).

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": "tb_product_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesProduct id (UUID) or torob.com product URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / product / description
      Previous value: -"Product id (the UUID from search cards, e.g. '57ea65ae-0798-4cd0-96a7-38d8af180345'), a '/p/<id>/...' path or a full torob.com product URL."New value: +"Product id (UUID) or torob.com product URL."
  2. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false. The one thing the description adds beyond them is "no request is sent", which usefully tells the agent this never touches the network despite openWorldHint=true, but it says nothing about the shape of the result or how malformed input is handled.

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 front-loaded sentence with zero filler; the operation and its key caveat arrive together.

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 utility with no output schema, the description covers the essentials. It still leaves an agent guessing what the returned "clean" value looks like (full URL vs path vs id) and what happens on invalid input.

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%, so the baseline applies. The description's mention of "path" slightly extends the schema, which only documents a UUID or full URL, and the plural "path or link" hints at additional accepted forms — a modest but real addition.

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 ("Clean torob.com URL for a product id, path or link") and distinguishes itself from data-fetching siblings via "no request is sent". It falls short of a 5 because "clean" is left to inference — normalize, strip tracking parameters, or canonicalize?

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?

The parenthetical implies this is a pure formatting utility rather than a lookup, which nudges the agent toward it before calling tb_product. However, no sibling is named and no explicit when-to-use or when-not-to-use condition is stated.

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

Deploy Server

Other Tools