Skip to main content
Glama
sepehr071

technolife-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Campaigns

tl_campaigns
Read-onlyIdempotent

List current campaigns or view a campaign's sections, carousels, links, and sample products by code, helping users browse current deals and promotion pages.

Instructions

List current campaigns, or show one campaign's sections and products.

  • Without code: campaign landings (code) and promotion pages (page_url) from the home page.

  • With code: the campaign's carousels with a few products each, and its links. Pass a page_url to tl_category_products to list all its products (products_in_carousel counts only the carousel).

Input Schema

NameRequiredDescriptionDefault
codeNoCampaign landing code from this tool's list, e.g. 'payday-technolife'. Omit to list current campaigns.
products_per_sectionNoProducts to show per carousel of a campaign.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • removedInput schema / properties / code / title
      Removed value: -"Code"
    • removedInput schema / properties / products_per_section / title
      Removed value: -"Products Per Section"
    • removedInput schema / title
      Removed value: -"tl_campaignsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "tl_campaignsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing that the return payload differs by mode (landings+page_url vs carousels+products+links) and warns that the carousel product count is partial. It omits pagination/rate details, but that gap is minor against the annotation coverage.

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

Conciseness4/5

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

Front-loaded with the two operating modes and then bulleted by case, so the agent gets the decision rule immediately. Every line earns its place, though the 'products_in_carousel' phrasing introduces a small term mismatch that costs a bit of clarity.

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?

With no output schema, the description carries the burden of describing return shapes, which it does for both modes. Combined with full schema coverage and complete safety annotations, an agent has everything needed to invoke it correctly.

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%, so the baseline is 3. The description goes beyond the schema by clarifying the consequence of omitting `code` and by scoping the meaning of the per-carousel product count ('counts only the carousel'). Minor naming drift ('products_in_carousel' vs `products_per_section`) tempers this slightly.

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 ('List current campaigns, or show one campaign's sections and products') and explicitly encodes the dual-mode behavior keyed on the presence of `code`. It distinguishes itself from the sibling `tl_category_products` by routing full product listing there, so an agent can tell the two apart without opening schemas.

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?

Gives explicit when-to-use branches: omit `code` to list landings/promotion pages, supply `code` to get carousels and links. It also names the alternative (`tl_category_products`) and the condition that selects it (listing all products of a carousel).

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