Skip to main content
Glama

Tenor Autocomplete

tenor_autocomplete
Read-onlyIdempotent

Return Tenor autocomplete completions for a partial search term (q); returns up to limit completed search phrases ordered by popularity.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "fun"
    },
    "name": "tenor_autocomplete"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
limitNo
localeNo
client_keyNo

Output Schema

NameRequiredDescriptionDefault
resultsNoAutocomplete suggestions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by stating results are capped at 'limit' and 'ordered by popularity', but it says nothing about rate limits, the client_key requirement, or locale effects, which are relevant for an open-world remote API call.

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?

A single front-loaded sentence that states the action, the key parameter, and the result shape with no filler. The parenthetical '(q)' is mildly redundant given the named input, but overall it is tightly written.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return structure need not be explained, and the popularity ordering is a useful addition. However, with two of four parameters undocumented and no guidance on choosing this tool over tenor_search, the definition is adequate rather than complete for a public API wrapper.

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 description coverage is 0% across four parameters, so the description must compensate. It explains 'q' (partial search term) and 'limit' (cap on returned phrases) but leaves 'locale' and 'client_key' entirely undocumented in both the schema and the description, which is a meaningful gap for a 4-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Return Tenor autocomplete completions') and names the input 'q' as a partial search term, so the agent knows exactly what the tool produces. It does not explicitly contrast itself with tenor_search, which is the nearest sibling an agent might confuse it with, so it stops short of a 5.

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: 'for a partial search term' signals you should call this when you have an incomplete query, but there is no explicit when-to-use/when-not statement and no named alternative (e.g. use tenor_search for full queries). An agent must infer the routing decision from the sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.