Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Shop info

tl_store_info
Read-onlyIdempotent

Read Technolife info pages as plain text for branches, shipping, returns, and payment methods; use it to quote shipping rules when exact costs require a logged-in address.

Instructions

Read one of Technolife's info pages as plain text.

Exact shipping cost needs a logged-in address: quote the rules. For other questions try tl_faq.

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": {
      "topic": "<topic>"
    },
    "name": "tl_store_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesbranches (stores, hours), shipping (methods, costs), returns, payment_methods.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / topic / description
      Previous value: -"branches (stores, hours, phones), shipping (methods, costs), returns (7-day guarantee), payment_methods."New value: +"branches (stores, hours), shipping (methods, costs), returns, payment_methods."
  2. Changed4 schema fields changedv0.3.0
    • changedInput schema / properties / topic / description
      Previous value: -"branches (physical stores, hours, phones), shipping (methods and costs), returns (7-day return guarantee), payment_methods (online, in store, installments)."New value: +"branches (stores, hours, phones), shipping (methods, costs), returns (7-day guarantee), payment_methods."
    • removedInput schema / properties / topic / title
      Removed value: -"Topic"
    • removedInput schema / title
      Removed value: -"tl_store_infoArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_store_infoDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: the response is plain text, and exact shipping cost cannot be obtained here — the agent must quote the rules instead. That is real behavioral value beyond the annotations, though nothing is said about page size or truncation.

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 short sentences with zero filler; the core action is front-loaded and the fallback routing follows immediately. Every clause carries information an agent would otherwise have to guess.

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 single-parameter, read-only lookup with a fully documented enum, the description supplies the response format (plain text) and the main usage caveat. The absence of an output schema is largely offset by "plain text", though nothing covers pagination or how much content a topic page contains.

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 enum values are already documented in the schema, so the schema carries the parameter burden. The description's note that the shipping topic yields rules rather than computed costs adds a useful nuance for that one value, but it does not explain the other three topics.

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?

"Read one of Technolife's info pages as plain text" gives a specific verb (read) and resource (info pages), and the enum in the schema narrows it to branches/shipping/returns/payment_methods. It does not fully differentiate from near-siblings like tl_faq or tl_shop_reviews beyond the pointer to tl_faq, leaving some overlap to be inferred.

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

Usage Guidelines4/5

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

"For other questions try tl_faq" is an explicit alternative with a selection condition, which is better than most. The when-not guidance is concrete for shipping (exact cost requires a logged-in address), but there is no guidance on when to prefer tl_shop_reviews, tl_find_location, or tl_campaigns for adjacent questions.

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