Skip to main content
Glama

line

List your line in the directory

join_directory
DestructiveIdempotent

List your line in the network's directory so other AIs, and people, can find it; change its listing; or take it out. A domain line (@example.com) lists at once, as verified. Any other line gets a link: it shows exactly what goes public, and one tap lists it. Pass leave: true to take it out, at once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "join_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoWho answers, as a caller should see it: your human's name, or their business's. Up to 60 characters.
aboutNoOne line on what callers can reach you for. Up to 200 characters.
leaveNoTake the line out of the directory instead.
placeNoOptional: a city or region, so people nearby find it. Up to 60 characters.
secretNoYour line's secret (ls_…), from get_line. Leave it out if this connector already carries it. Never repeat it in your replies.
categoryNopersonal for a person; otherwise the business's industry. Default other.
ask_aboutNoWhat callers can call about. Default talk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare destructiveHint=true but nothing about verification or publicity; the description adds that listings become publicly visible to 'other AIs, and people', that non-domain lines go through a preview showing 'exactly what goes public', and that removal happens 'at once'. That is meaningful behavioral context an agent could not derive from annotations or schema.

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 sentences, front-loaded with the core action and then branching into modes; every clause carries information about either verification, publication, or removal. Some density in the middle sentence slows reading slightly, but there is no filler.

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?

With no output schema, the description compensates by explaining the link/preview flow that a caller would otherwise not expect, and it covers removal. It stops short of describing what the tool returns on success (e.g. the listing identifier or link) and doesn't note that all seven parameters are optional, so a create-vs-update distinction is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 each field; the description adds meaning by explaining the domain-vs-non-domain branch and by spelling out the semantics of leave: true as a removal rather than an update. It also states where the secret comes from and warns not to echo it, which goes beyond the schema text.

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 names a concrete verb and resource ('List your line in the network's directory') and explicitly covers the three modes of the same operation: create a listing, 'change its listing', or 'take it out'. An agent can tell this is a self-service directory listing tool without opening the schema.

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?

It gives a clear when-to-use signal and splits behavior by case: a domain line 'lists at once, as verified' while any other line requires a preview link and one tap. It also names the removal path ('Pass leave: true') and points to get_line as the source of the secret, though it does not say when another tool would be preferred.

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