Skip to main content
Glama
Sign In

Trendswap AI

by io.github.GptsApp
OverviewDiscussionsAdmin

Server Details

AI face swap and viral meme video generation MCP server.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
97.5% over 20 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool in the set, there is no possibility of overlap or misselection between tools. The lone tool's purpose is unambiguous.

Naming Consistency5/5

list_templates follows a clear verb_noun snake_case convention. With one tool there is no inconsistency to introduce, though the convention cannot be verified against siblings.

Tool Count2/5

A single tool is very thin for a server that appears to be a template/video platform. Even a read-only browsing surface would typically include fetching a template by ID or searching/filtering, so one tool under-serves the apparent scope.

Completeness2/5

Only a list operation exists; there is no get_template, search/filter, or any way to retrieve details, preview, or use a specific template. Agents hitting a listed template ID have no follow-up operation, creating a dead end.

Available Tools

1 tool
list_templatesA
Read-onlyIdempotent
Inspect

List all available viral video templates on Trendswap with their template IDs, descriptions, and preview URLs. Supports 4 global languages. No authentication required.

NameRequiredDescriptionDefault

No parameters

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant context beyond that: no authentication is required and four global languages are supported. It does not mention rate limits or pagination, keeping it short of 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?

Three tight sentences with zero filler. The core action and returned data are front-loaded, and the language/auth details follow as supporting facts.

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 parameterless, read-only list tool with no output schema, the description compensates by naming the fields returned and stating the language and auth situation. Nothing an agent needs in order 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.

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description correctly avoids inventing filtering options that the empty schema does not support.

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 all available viral video templates on Trendswap') and enumerates the returned fields (template IDs, descriptions, preview URLs). No sibling tools exist, so no differentiation is required; the scope is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied — an agent can infer this is the discovery call for templates — and there are no alternatives to weigh. The 'No authentication required' clause does help an agent decide it can call this immediately, but no explicit when/when-not guidance is given.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • Removedcreate_generation_job
    • Removedget_credits_balance
    • Removedget_job_status
  2. 4 tool updates
    • First observedcreate_generation_job
    • First observedget_credits_balance
    • First observedget_job_status
    • First observedlist_templates

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources