Skip to main content
Glama

Nyt

by io.github.pipeworx-io

Movie Reviews

movie_reviews
Read-onlyIdempotent

Search New York Times movie reviews. Optionally filter by query or critics picks. Returns title, summary, byline, publication date, and URL. Example: movie_reviews({ query: "dune", critics_pick: true })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch query — movie title or keyword (optional).
_apiKeyNoOptional — your own NYT API key for higher limits; omit to use the shared Pipeworx key.
critics_pickNoIf true, only return reviews flagged as NYT Critics’ Picks (optional).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate safe read-only behavior. The description adds value by listing return fields (title, summary, byline, publication date, URL) and includes an example, providing useful context beyond the annotations.

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?

The description is two sentences plus an example, front-loaded with the action. Every word serves a purpose, and the example illustrates usage efficiently.

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?

Given the absence of an output schema, the description explicitly lists return fields. The input schema is fully documented, and the description provides a complete overview of what the tool does, its optional parameters, and a usage example.

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?

While the schema already covers all three parameters (100% coverage), the description provides a concise summary of their purpose and an example usage, which aids understanding without repeating schema details.

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 verb 'Search' and the resource 'New York Times movie reviews'. It specifies optional filters (query or critics picks) and provides an example, making the tool's purpose unambiguous and distinct from broader search tools like 'search_articles'.

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?

The description clearly conveys the tool's scope (movie reviews) with optional filters, but does not explicitly state when to avoid this tool or mention alternative tools. The context is clear enough for appropriate selection.

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

All Nyt 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

A3.6/5.0
Disambiguation2/5

ask_pipeworx and ask_pipeworx_beta are explicitly identical today, and ask_pipeworx_grounded, deep_research, and validate_claim all route to the same underlying sources with overlapping question-answering purposes. Entity-focused tools like entity_profile, compare_entities, recent_changes, and resolve_entity also have fuzzy boundaries that make selection error-prone.

Naming Consistency2/5

Names mix conventions: verb_noun (list_subscriptions, search_articles, generate_llms_txt), bare verbs (remember, recall, forget), noun phrases (polymarket_arbitrage, pipeworx_trending, entity_profile), and an ask_* family with beta/grounded variants. There is no consistent verb or noun pattern across the set.

Tool Count2/5

With 35 tools, the surface is well above the 15-tool threshold for a focused server, and most tools are unrelated to the NYT domain implied by the server name. The breadth reflects a broad data-platform grab bag rather than a scoped, intentional tool set.

Completeness4/5

The query side is unusually complete: single-lookup, grounded lookup, deep research, claim validation, entity resolution, comparison, profile, change-feed, discovery, memory, and subscription lifecycle tools are all present. Minor gaps remain, such as no direct NYT article fetch by URL and no update path for stored memories, but agents can work around them.

Resources