Skip to main content
Glama
@elido/mcp-server

@elido/mcp-server

Official
by elidoapp

query_analytics

Retrieve click-count timeseries for a workspace or single link, bucketed by hour or day in a specified IANA timezone.

Instructions

Click-count timeseries for a workspace or single link. Buckets in the supplied IANA timezone.

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": "query_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoISO date YYYY-MM-DD. Inclusive.
tzNoIANA name, e.g. Europe/Berlin. Default UTC.
fromNoISO date YYYY-MM-DD. Inclusive.
link_idNoOptional. Restricts the timeseries to one link; otherwise returns the workspace total.
intervalNoday

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses two behavioral traits: results are bucketed as a timeseries, and bucketing respects the supplied IANA timezone. However, it omits critical behavior for a tool with zero required parameters — notably the default date range when from/to are omitted — as well as any read-only framing, result size, or bucketing granularity beyond the interval enum.

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

Conciseness5/5

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

Two short sentences with zero filler, and the core purpose is front-loaded ahead of the timezone detail. Nothing is repeated or padded.

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 5-parameter analytics tool with no annotations and no output schema, the description is thin. Because all parameters are optional, an agent needs to know the default date range and what a bucket actually contains (counts only? per-link breakdown?), and neither is covered; the description does not compensate for the missing output schema either.

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 80%, so the baseline is 3. The description reiterates the timezone-to-bucket mapping and the workspace-vs-link scoping, both of which the schema already states, so it adds little meaning beyond the structured fields. The one genuinely useful reinforcement is that bucketing (not just filtering) follows the tz parameter.

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-like resource ('Click-count timeseries') and its scope ('for a workspace or single link'), which is enough to distinguish it from the listed siblings (create_link, generate_qr, list_links, list_workspaces) since none of those return analytics. It stops short of naming any sibling explicitly, so it earns a 4 rather than 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: the reader can infer this is the tool for click analytics in a date range, and the phrase 'workspace or single link' implies a scope choice. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g., that link-level analytics require a link_id from list_links).

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