Skip to main content
Glama

track_social_momentum

Monitor shifts in social media activity for a token over a chosen timeframe to gauge community sentiment and detect rising or fading interest.

Instructions

Track changes in social media activity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYes
timeframeNoHours to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'track changes' but does not explain what data sources are used, whether the operation is read-only, how often data updates, or what the return format looks like.

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 a single front-loaded sentence with no wasted words. It is appropriately sized for a short definition, even though it is underspecified.

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

Completeness2/5

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

For a tracking tool with two parameters, one required and undocumented, no output schema, and no annotations, the description is incomplete. It lacks key details about the token parameter, timeframe behavior, and how it relates to sibling analytics tools.

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 only 50%, and the required 'token' parameter has no description at all. The description does not add meaning beyond the schema, leaving the token parameter's purpose and the timeframe's effect unclear.

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

Purpose3/5

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

The description states a verb ('track') and a resource ('social media activity'), giving a general idea of the tool. However, it is vague about what changes are tracked and does not distinguish this tool from siblings like get_social_sentiment or get_influencer_activity.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_social_sentiment or get_influencer_activity. There is no mention of context, prerequisites, or exclusions.

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