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

@lodd/mcp-server

by hholen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_site

Register a new website to obtain analytics tracking code, site ID, and secret for first-party web analytics.

Instructions

Register a new website for analytics tracking. Returns the site ID, tracking secret, and the script tag to embed.

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": {
      "name": "<name>",
      "domain": "<domain>"
    },
    "name": "create_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name for the site (e.g. 'My Blog')
domainYesDomain to track (e.g. 'example.com'). Do not include https:// or www.

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?

With no annotations, the description notes that it returns site ID, tracking secret, and script tag. However, it does not disclose idempotency, error behavior for duplicate domains, or authorization requirements.

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 concise sentences with no wasted words. The key action and return values are front-loaded.

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?

The description explains the return values adequately given no output schema. However, it omits behavioral details like idempotency and potential errors, which would enhance completeness.

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%, so the schema already documents both parameters well. The description adds no additional semantic context beyond what the schema provides.

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 action ('Register a new website for analytics tracking') and specifies the resource (website). It distinguishes itself from sibling tools that list or retrieve data.

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 creation but does not provide explicit guidance on when to use this tool over alternatives like creating an API key or annotation, nor does it mention prerequisites or restrictions.

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