Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search FAQ

tl_faq
Read-onlyIdempotent

Search Technolife's help-center FAQ for policy answers. provide a Persian word to get matching questions and answers; try another word or store info if no matches.

Instructions

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

Use for policy questions. Single words match best; an empty list means try another word or tl_store_info.

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.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely new behavioral context: an empty result list is the expected no-match signal and suggests retry or an alternative tool.

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 and a hint line; the core action and return shape are front-loaded with no filler.

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?

With no output schema, the description correctly states what is returned (questions plus plain-text answers) and covers the empty-result case. Enough for a one-parameter lookup tool, though it could note approximate matching or language scope.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already gives an example and minLength, so baseline is 3. The description adds real query-shaping guidance ('single words match best'), which is not derivable from the schema.

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 ... help-center FAQ') plus what comes back ('matching questions with plain-text answers'). It names the tl_store_info fallback but does not differentiate itself from search-like siblings tl_search and tl_suggest.

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?

'Use for policy questions' gives clear context, and 'empty list means try another word or tl_store_info' supplies an explicit fallback path. No when-not-to-use guidance relative to tl_search/tl_suggest, but the routing hint is concrete.

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