Skip to main content
Glama
technolife-mcp

technolife-mcp

by sepehr071

Search FAQ

tl_faq
Read-onlyIdempotent

Search Technolife's help-center FAQ with one or two Persian keywords to find matching questions and plain-text answers.

Instructions

Search Technolife's help-center FAQ and return matching questions with plain-text answers.

Single words match best; an empty list means try another word or tl_store_info.

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": {
      "query": "<query>"
    },
    "name": "tl_faq"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesOne or two Persian words, e.g. 'ارسال', 'اقساط'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • changedInput schema / properties / query / description
      Previous value: -"One or two Persian words, e.g. 'ارسال', 'اقساط', 'مرجوعی', 'گارانتی'."New value: +"One or two Persian words, e.g. 'ارسال', 'اقساط'."
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"tl_faqArguments"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "tl_faqDictOutput",
      -  "type": "object"
      -}New value: +null
  2. 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, non-destructive, open-world behavior, so the safety profile is covered. The description still adds value beyond them by disclosing the empty-result semantics and the matching behavior (keyword-style, single-word queries), which the annotations say nothing about. It does not discuss rate limits or result caps, keeping it below 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 with no filler: purpose and return shape first, then query strategy and the empty-result fallback. Every clause carries actionable information for the caller.

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 no output schema, the description covers what it does, what it returns, and what an empty result means. Minor gaps remain around result ordering or match breadth, but nothing needed to call 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 query param is fully documented with type, minLength and Persian examples, so the baseline is 3. The description's 'single words match best' adds mildly useful retrieval-strategy meaning but largely restates the schema's 'one or two Persian words' guidance.

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?

States a specific verb and resource ('Search Technolife's help-center FAQ') plus the return shape ('matching questions with plain-text answers'), which an agent can distinguish from product-search siblings like tl_search. It does not explicitly say how it differs from near-neighbors such as tl_suggest or tl_seller, so it stops short of a 5.

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?

Gives concrete query guidance ('Single words match best') and a fallback path when the result set is empty ('try another word or tl_store_info'), which is a real routing hint rather than vague context. There is no statement of when NOT to use it versus the other search-family siblings, so it is clear context without exclusions.

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