Skip to main content
Glama
Sign In
@lodd/mcp-server

@lodd/mcp-server

by hholen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_snapshot

Compare today's traffic metrics against yesterday's, including visitors, top referrer, top country, and duration trends for a given site.

Instructions

Quick today vs yesterday comparison: visitors, top referrer, top country, and duration trends

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": {
      "site": "<site>"
    },
    "name": "get_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite domain or UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.15

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses the comparison scope (today vs yesterday) but lacks details on auth requirements, rate limits, or behavior with missing data.

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 a single, front-loaded sentence with no unnecessary words, efficiently conveying the tool's purpose and key metrics.

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?

For a simple snapshot tool with one parameter and no output schema, it lists the returned metrics, but lacks details on return format or structure, which would be helpful for an AI agent.

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 100% with one parameter (site) already described. The description adds no additional parameter details, meeting baseline for high coverage.

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 it provides a quick today vs yesterday comparison of specific metrics (visitors, top referrer, top country, duration trends), distinguishing it from more detailed analytics tools like get_analytics or get_timeseries.

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?

The description implies usage for a quick snapshot, but does not explicitly state when to use this tool over alternatives or when not to use it. No exclusions or alternative tools are mentioned.

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

Deploy Server

Other Tools