Skip to main content
Glama

Tenor

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations (readOnlyHint, idempotentHint) are already present. The description adds valuable behavioral context: returns top-N tools with full schemas and curated examples, ready to call directly. No contradiction with annotations.

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?

The description is comprehensive and front-loaded with the core purpose, but slightly verbose with the long list of domains. Still, every sentence adds value, and structure is clear.

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?

Tool is simple with no output schema, but the description fully explains return values (tool names, descriptions, schemas). Parameter coverage is 100%. No gaps given tool complexity.

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 coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions. It mentions aliases, but schema already covers them. No additional param documentation needed.

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 states 'Find tools by describing the data or task' with specific examples of domains (SEC filings, FDA drugs, etc.). It clearly distinguishes itself from sibling search tools by focusing on tool discovery and returning full schemas for immediate use.

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?

Explicitly says 'Call this FIRST when you have many tools available' and provides specific use cases like browsing or searching for tools. This gives clear when-to-use guidance and implies it's a starting point before using other tools.

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

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

Several tools have nearly identical purposes: autocomplete and search_suggestions both return query completions, ask_pipeworx and ask_pipeworx_beta are currently identical, and ai_visibility_check overlaps with scan_competitor_ai_presence. The detailed descriptions help for some, but the overlapping clusters create real confusion for an agent selecting a tool.

Naming Consistency3/5

Naming is a mix of single-word nouns (search, featured, posts, categories) and snake_case verb phrases (resolve_entity, compare_entities, ask_pipeworx), with modifier suffixes like _beta and _grounded. While the snake_case is consistent where used, the overall pattern is not uniform across the server.

Tool Count2/5

38 tools is far too many for a server named 'Tenor' whose core GIF API needs only a handful. Much of the surface belongs to Pipeworx data, polymarket analytics, memory, and subscriptions—scope that belongs in a different server or a clearly separated package.

Completeness5/5

The Pipeworx side is remarkably complete: query (ask_pipeworx), grounded answers, deep research, entity profiles, comparisons, validation, discovery, memory, subscriptions, and specialized polymarket tools all cover their domain thoroughly. The Tenor side has search, browse, categories, trending, suggestions, and post retrieval—no critical dead ends.

Resources