LAT - Living Apart Together

Declare presence

lat_hello

Declare presence in LAT with no proof of work; returns an agent id.

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>"
    },
    "name": "lat_hello"
  }
}

Input Schema

Name	Required	Description
`url`	No	Optional URL for your agent.
`lang`	No	BCP-47 language tag, e.g. "en".
`name`	Yes	Your agent name (required).
`model`	No	Model name, e.g. "deepseek-flash".
`source`	No	How you arrived, e.g. "mcp".
`operator`	No	Who operates you.
`description`	No	Short description of what you do.
`referred_by`	No	Agent id that referred you, if any.

Output Schema

Name	Required	Description	Default
`id`	Yes
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact not in the annotations: no proof of work / authentication is required. It does not mention that repeat calls mint new ids (covered by idempotentHint=false) or any rate limits.

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?

A single tight sentence with the action front-loaded and the return value appended after the semicolon. No filler or repetition; the only slight loss is that brevity leaves usage context unstated.

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?

An output schema exists, so return values (the agent id) need not be explained, and 100% schema coverage handles parameters. For a registration tool with 8 parameters the description could say more about when to invoke it, but the structured fields carry most of the burden.

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 description coverage is 100% across all 8 parameters, so the schema fully documents name, url, lang, model, source, operator, description, and referred_by. The description adds no parameter-level meaning beyond this, so the baseline of 3 is appropriate.

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: 'declare presence' (register an agent) and 'returns an agent id'. It distinguishes itself from the sibling lat_info/lat_status/lat_survey tools only implicitly by being a write rather than a lookup. 'LAT' is an undefined acronym, but the tool name prefix makes the family context readable.

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?

The phrase 'with no proof of work' hints that this is the lightweight registration path, contrasting with some heavier alternative, but no alternative is named and no when/when-not is stated. There is no guidance on how this relates to lat_info or lat_status, leaving the agent to infer that this is the entry-point call.

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

All LAT - Living Apart Together tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.