Skip to main content
Glama
Sign In
torob-mcp

torob-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Shop presence

tb_presence
Read-onlyIdempotent

See how widely a product is sold across online and in-person shops, including installment and warranty sellers and price windows, by entering a product ID or Torob URL.

Instructions

How widely a product is sold: online shops, in-person stores, installment and warranty shops, price window.

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_presence"
  }
}

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

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds the useful signal that results span online shops, physical stores, installment/warranty sellers, and a price window – behavioral context beyond the annotations. It does not describe result shape or whether the answer is a count, list, or summary.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short fragment with no wasted words, but the terseness comes at the cost of precision: no verb, and 'price window' is left unexplained. Short is not the same as well-structured here.

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?

With one required parameter, no output schema, and full annotation coverage, the definition is nearly complete for invocation. However, it never explains what 'how widely' means operationally (counts? shop list? range?) or what a 'price window' is, leaving the return semantics ambiguous.

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 'product' parameter is fully documented (UUID or torob.com URL), so the schema carries the burden. The description adds nothing about how the product input affects the presence result, so baseline 3 applies.

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

Purpose3/5

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

The description identifies the resource as how widely a product is sold across shop types, but it is a noun phrase without a verb, and terms like 'price window' and 'presence' are not defined. An agent can guess it returns availability/distribution info but cannot state precisely what the tool returns versus tb_offers or tb_stores.

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?

No when-to-use guidance and no exclusions are given, despite many plausible siblings (tb_offers, tb_stores, tb_find_shops, tb_sellers, tb_cheapest) that could be confused with it. The agent must infer that 'presence' means distribution breadth rather than price comparison.

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