Skip to main content
Glama
Sign In

Hailbell

by com.hailbell.api
OverviewDiscussionsAdmin

get_context

Read-only

What to know before writing a message: the current time where the audience is, their countries, the hours they usually use the app, upcoming occasions in their countries (festivals, holidays and sales worldwide, such as Diwali, Lunar New Year, Eid, Christmas and Black Friday, each with a kind and a tier, and the app's own dates), the app's daily cap and quiet hours, and the {{variables}} you can use.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow far ahead to list occasions. Default 14
appIdNoThe app to act on, from list_apps. Optional when the key belongs to one app.
platformsNoSeveral platforms of one app in one campaign: "all", or a list of "ios", "android", "web" (or App IDs). Each person gets it once. Omit (with no productId) for the one platform of appId.
productIdNoThe whole app (productId from list_apps), for a campaign across its platforms. Same as appId of any platform with platforms "all".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by enumerating what the payload contains (quiet hours, daily cap, occasion kind and tier, app's own dates), which tells the agent what decisions this data supports. It does not state freshness, caching, or cost, keeping it out of 5 territory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core framing is front-loaded, which is good, but the single sentence sprawls into a long parenthetical naming five example festivals. Those examples aid recognition of the occasions concept but are the kind of detail that could be trimmed without losing meaning.

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

Completeness4/5

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

With no output schema, the description must convey the return contents, and it does so thoroughly across all seven data categories. The main gap is that the platforms/productId campaign-scoping behavior is left entirely to the schema, and the relationship to sibling tools like coming_up is unaddressed.

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 100%, so all four parameters (days, appId, platforms, productId) are already documented in the schema. The description only obliquely touches the 'days' horizon via 'upcoming occasions' and says nothing about the campaign-targeting parameters. Baseline 3 applies since the schema carries the load.

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 opens with a concrete framing ('What to know before writing a message') and enumerates the exact resources returned: audience-local time, countries, typical usage hours, upcoming occasions, daily cap, quiet hours, and available variables. That is far more specific than a restatement of the name. It falls short of a 5 because it never distinguishes itself from the sibling 'coming_up', which plausibly overlaps on the occasions portion.

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?

'Before writing a message' implies the usage context (pre-composition/preview), but there is no explicit when-not guidance and no named alternative such as coming_up or estimate_audience. The agent must infer the boundary from sibling names alone.

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

All Hailbell toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources