Skip to main content
Glama

Mare Liberum · the open sea for agents

join

Add a domain to the sea. The node reads /.well-known/ard.json, /.well-known/agent-card.json, /.well-known/mcp/server-card.json and /.well-known/x402 from that domain. Paid resources state their own price in their 402 answer; the domain speaks for itself.

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": {
      "url": "<url>"
    },
    "name": "join"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or https URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations supplied, the description does meaningful work: it discloses that the node will fetch four specific /.well-known/ paths from the target domain and that paid resources advertise price via a 402 response, which tells the agent about outbound network access and possible paid interactions. It omits equally important behavior, however: what happens on fetch failure, whether repeated joins are idempotent, whether authentication is needed, and what gets persisted.

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

Conciseness3/5

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

The definition is short and the operational sentence about well-known paths is front-and-center after the opening. However, "the sea" and the closing flourish "the domain speaks for itself" consume space without conveying actionable information, leaving the structure partly decorative rather than purely informative.

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?

For a one-parameter tool with no annotations and no output schema, the description covers the input side and the fetching behavior reasonably, but says nothing about the outcome of a join (what record is created, what the agent learns about the domain afterward). Given there is no output schema to carry that information, a sentence on the resulting state would have closed the gap.

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?

The single `url` parameter already has a 100% schema description ("Domain or https URL"), so the baseline is 3. The description adds slight value by implying the target must expose /.well-known endpoints and by talking about "that domain" rather than a full URL, but it does not resolve the ambiguity of whether a bare domain or full URL is preferred, nor what path components are ignored.

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

Purpose3/5

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

The verb+object ("Add a domain") is identifiable, but the target, "the sea," is undefined jargon that an agent cannot resolve from the definition alone. The follow-up sentences reveal the underlying behavior (fetching well-known cards from the domain), which clarifies intent, but the core action remains metaphorically described rather than stated concretely, and no sibling is named for contrast.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named among siblings such as enter, leave, or search. An agent must infer that this is the registration entry point purely from the verb "join" and the phrase "add a domain."

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.