Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Shop info

tl_store_info
Read-onlyIdempotent

Read Technolife store branches, shipping rules by city, returns, and payment methods as plain text. Use it to answer policy questions when exact shipping costs need a logged-in address.

Instructions

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

Use for stores, shipping rules per city, returns and payment. Exact shipping cost needs a logged-in address, so quote the rules. For other questions try tl_faq.

Input Schema

NameRequiredDescriptionDefault
topicYesbranches (stores, hours, phones), shipping (methods, costs), returns (7-day guarantee), payment_methods.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is known. The description adds genuinely new behavioral context: output is plain text, and exact shipping cost cannot be resolved without a logged-in address, so the agent should quote rules instead. That auth/limitation disclosure is the value-add; return formatting and size are otherwise unspecified.

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?

Three short sentences, purpose front-loaded, alternative routing last. Every sentence earns its place with no repetition of schema content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with no output schema, the description covers what it does, what it returns (plain text), when to use it, when to use the sibling instead, and the one behavioral caveat (auth-gated exact costs). Nothing needed to invoke it correctly is missing.

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 the single enum already documents all four topic values, so the baseline is 3. The description restates those topics with slight added nuance ('shipping rules per city') but adds no syntax or format detail beyond the schema.

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

Purpose5/5

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

States a specific verb and resource ('Read one of Technolife's info pages') and enumerates the covered topics (stores, shipping rules per city, returns, payment), which maps directly onto the enum. It also names the sibling it is not, tl_faq, so an agent can distinguish it without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('for stores, shipping rules per city, returns and payment') plus an explicit alternative and its trigger ('For other questions try tl_faq'). It even warns about the auth prerequisite, telling the agent to quote rules rather than attempt an exact cost lookup.

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