Skip to main content
Glama

register_site

Idempotent

Add a website to your LiftMCP organisation as a Property and get the server card to publish on it. Needs your organisation API key in the Authorization header. Safe to repeat: a site already added is found, not added twice. Next: publish the card exactly as given at the address given, then call verify_site.

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

Input Schema

NameRequiredDescriptionDefault
domainYesThe site, e.g. example.com or https://www.example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the repeat-safety sentence mostly reinforces structured data — but it adds specificity ('found, not added twice'). The auth requirement and the fact that a server card is produced are genuine additions not present in annotations.

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

Conciseness4/5

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

Three compact sentences, front-loaded with purpose, then prerequisite, then next steps. Slightly awkward phrasing ('the card exactly as given at the address given') but no wasted content.

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

Completeness5/5

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

For a single-parameter mutation with rich annotations and no output schema, the description covers auth, side effect (server card returned), idempotency, and the required verification handoff. Nothing an agent needs to call it correctly is missing.

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?

Only one parameter, whose schema description is already at 100% coverage with example formats. The description adds no syntax or validation detail beyond what the schema provides, so baseline 3 applies.

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 and resource ('Add a website ... as a Property') plus the immediate outcome (a server card to publish). An agent can distinguish it from verify_site, which the description frames as the downstream step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a prerequisite (organisation API key in the Authorization header), a repeat-safety note, and an explicit follow-up sequence: publish the card, then call verify_site. It stops short of naming when not to use it, so it doesn't reach the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources