Skip to main content
Glama
logly-uk

Logly MCP server

Official
by logly-uk

logly_realtime

See which visitors are currently active on a site. Provide the site ID to fetch real-time data from the last few minutes.

Instructions

Visitors currently active on a site (real-time, the last few minutes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesLogly site ID (slug). Call logly_list_sites to discover it.

Implementation Reference

  • index.js:76-81 (registration)
    Registration of the 'logly_realtime' tool via the 'tool()' helper function. Line 76-81 define the tool name, description, schema (site arg), and the handler callback.
    tool(
      "logly_realtime",
      "Visitors currently active on a site (real-time, the last few minutes).",
      { site: siteArg },
      ({ site }) => loglyApi(`/api/sites/${encodeURIComponent(site)}/active`)
    );
  • index.js:80-80 (handler)
    Handler function for logly_realtime: makes an API call to `/api/sites/{site}/active` using the loglyApi helper.
    ({ site }) => loglyApi(`/api/sites/${encodeURIComponent(site)}/active`)
  • Schema for logly_realtime: expects a 'site' argument (string, described as 'Logly site ID (slug)') — defined via the shared 'siteArg' on line 47.
    { site: siteArg },
  • The 'tool()' helper that wraps server.tool() with error handling. All tool registrations (including logly_realtime) use this helper.
    function tool(name, description, shape, fn) {
      server.tool(name, description, shape, async (args) => {
        try {
          return { content: [{ type: "text", text: await fn(args || {}) }] };
        } catch (e) {
          return { content: [{ type: "text", text: "Error: " + e.message }], isError: true };
        }
      });
    }
Behavior2/5

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

No annotations are provided, so the description must cover behavior. It only states the time scope (real-time, last few minutes) but does not disclose what exactly is returned (count, list, objects), data freshness guarantees, or any limitations. For a tool with no annotations, this is insufficient.

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?

The description is one concise sentence that is front-loaded and every word adds value. No extraneous 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?

Given the tool's simplicity (one parameter, no output schema), the description is mostly adequate but leaves ambiguity about the return format (count vs. list). It could be more complete by specifying the output type or data structure.

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%, and the parameter description already explains the site ID slug and directs the agent to call logly_list_sites. The tool description adds no additional meaning beyond what the schema provides, so it meets the baseline of 3.

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

Purpose5/5

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

The description clearly states the tool retrieves visitors currently active on a site in real-time over the last few minutes. It specifies the verb (visitors active), resource (site), and temporal scope, distinguishing it from siblings like logly_stats which likely provide historical data.

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 lacks any guidance on when to use this tool versus alternatives (e.g., logly_events, logly_stats). No differentiation criteria or context of use is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly-uk/logly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server