Skip to main content
Glama

Caelara Labs Social Analytics

engagement_rate_calc

Compute engagement rate metrics and benchmark tier

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": {
      "followers": "<followers>",
      "likes": "<likes>"
    },
    "name": "engagement_rate_calc"
  }
}

Input Schema

NameRequiredDescriptionDefault
likesYesLikes
savesNoSaves
viewsNoViews
sharesNoShares
commentsNoComments
followersYesFollower count

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden and does very little: it does not state the engagement-rate formula (likes/followers vs. all-interactions/followers vs. per-view), what 'benchmark tier' means or where thresholds come from, whether optional metrics like saves/shares/views change the calculation, or whether results are deterministic. For a metric-definition tool, the formula is the single most important behavioral fact and it is absent.

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 clause with zero filler. Nothing is wasted, though the brevity tips into under-specification rather than tightness.

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?

Six parameters, no output schema, and no annotations mean the description is the only place formula, tier semantics, and optional-input handling could be explained, and none of that is present. An agent can call it, but cannot predict or interpret the result.

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 nominally 100%, but each parameter is documented only by a one-word label ('Likes', 'Saves', 'Follower count'), which adds no real meaning. The description could compensate by explaining which param combos produce which engagement metrics or whether missing optional params are treated as zero, but it does not. Baseline 3 applies since the schema at least enumerates the inputs.

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?

States a specific verb+resource: 'Compute engagement rate metrics and benchmark tier.' An agent can tell this is a computation/benchmarking tool rather than an auditing or extraction tool, though the description never names which metrics or platform conventions it applies.

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?

No when-to-use guidance, no prerequisites, and no reference to any sibling. The agent is left to guess whether this belongs before or after tools like creator_profile_composite or video_viral_audit_composite.

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.

Resources