MEME

Overview Schema Source Related Servers Discussions Admin

Get trend context

get_trend

Fetches context for a single trend—signals, cultural references, developer relevance, and sanitized generation context—so you can evaluate and use it in meme creation.

Instructions

Full context for one trend: signals, cultural references, developer relevance analysis, and the sanitized context block used for generation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trendId": "<trendId>"
    },
    "name": "get_trend"
  }
}

Input Schema

Name	Required	Description	Default
`trendId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return contents in useful detail, which substitutes for the absent output schema, but it says nothing about behavior on an invalid or unknown trendId, whether this is a pure read, or any auth/side-effect profile.

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 lists the payload contents without filler. It is appropriately sized, though the colon-list style reads as a fragment rather than a complete sentence and carries no routing information.

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?

With no annotations and no output schema, the description does the heavy lifting on what is returned, which is the biggest gap it could have filled. It still leaves the mandatory trendId unexplained and gives no usage context, so it is adequate but incomplete for a detail-fetch tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 0% and the single parameter trendId is never explained: the description does not say it is a trend identifier, where to obtain it, or its format. 'One trend' only vaguely hints at the key's meaning, leaving the agent to infer the rest from the schema's type alone.

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-resource pair ('Full context for one trend') and enumerates the constituent parts (signals, cultural references, developer relevance analysis, sanitized context block), so an agent knows exactly what it returns. The phrase 'one trend' implicitly contrasts with the plural sibling get_trends, but the contrast is never made explicit.

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

Usage Guidelines2/5

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

There is no statement of when to call this instead of get_trends, no prerequisite such as where trendId must come from, and no exclusion criteria. The only hint is the reference to 'the sanitized context block used for generation', which weakly implies a detail/generation-inspection use case rather than explicit guidance.

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