Skip to main content
Glama

Tmdb

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds value by explaining scoping (anonymous IP, BYO key hash, account ID) and behavior when omitting key (list all). No contradictions.

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 zero wasted words. Purpose is stated first, then usage guidance, then scoping. Very efficient.

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?

Given the simplicity (1 param, no output schema, full annotations), the description covers purpose, scoping, and pairing with other tools. Sufficient for an agent to use correctly.

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 has 100% coverage with description for 'key'. The tool description largely restates schema info (omit to list all). Baseline is 3 due to high coverage; description adds minimal extra meaning.

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?

The description clearly states the tool retrieves a saved value or lists keys, with specific verb ('retrieve'/'list') and resource ('saved via remember'). It distinguishes from sibling tools 'remember' and 'forget' by naming them explicitly.

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?

Provides explicit guidance on when to use (look up stored context) and mentions scoping to identifier. Also references companion tools. However, does not explicitly state when not to use or list direct alternatives beyond remember/forget.

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

All Tmdb toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

The tool set blends two unrelated domains (TMDB and Pipeworx). Among Pipeworx tools, several overlap heavily (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, suggest_questions) with vague boundaries, making it hard for an agent to pick the right one. TMDB tools are distinct but the overall mixture creates confusion about which domain a request belongs to.

Naming Consistency3/5

All tools use snake_case, which is consistent. However, naming styles vary widely: TMDB tools use simple noun or verb-first names (movie, search_movie, discover_tv), while Pipeworx tools use longer descriptive phrases with prefixes (ask_pipeworx, polymarket_arbitrage, entity_profile). The pattern is not predictable across the set.

Tool Count2/5

50 tools is excessive for a server named 'Tmdb'. Only about 18 tools are actually TMDB-related; the remaining 32 belong to the Pipeworx ecosystem. This inflates the count and makes the server feel bloated and unfocused, far beyond a well-scoped TMDB server.

Completeness3/5

The TMDB portion is quite complete (search, discover, details, credits, recommendations, trending, genres, configuration). However, the server's overall scope is muddled—it tries to cover two disjoint domains, so no single domain feels fully fleshed out. There are also some missing TMDB features (e.g., upcoming/now playing) that would require extra discovery. The Pipeworx tools cover data broadly but overlap in coverage.

Resources