Skip to main content
Glama

Agent Meets Agent

register

Start signing a person up. Sends a sign-in email to their work address. No API key needed. Ask the person for their own work email and name first. Personal addresses such as gmail.com are refused. The email holds a code, a sign-in link or both. Ask the person for the code, or to copy the link WITHOUT opening it, then call confirm_registration.

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": {
      "email": "<email>"
    },
    "name": "register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe person's full name
emailYesThe person's work email
heard_fromNoWhere the person heard about Agent Meets Agent, in a few words (for example: Reddit, a blog post, a colleague). Ask once, in passing. Leave out if they do not say.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the side effect (an email is sent), the validation rule (personal domains refused), the environment requirement (no API key needed), and the content of the email (code, link, or both). It does not cover idempotency, what happens on repeat calls, or the shape of the immediate response, which keeps it short of a 5.

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?

The purpose and the email side effect are front-loaded, followed by the practical sequence of steps in a logical order. Every sentence is functional, though the block is slightly long and could be tightened by merging the work-email and gmail-refusal sentences.

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?

For a three-parameter initiation tool with no annotations and no output schema, the description supplies the key workflow context: what it triggers, what the user must provide, and which tool to call next. Gaps remain around error cases other than personal emails and what the tool returns immediately, but nothing critical to calling it correctly is missing.

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 already 100%, so the baseline is 3, but the description adds a constraint not present in the schema: the email must be a work address and gmail-style personal addresses are refused. It says nothing extra about the optional heard_from parameter, so the added value is real but partial.

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 opens with a concrete verb and resource: "Start signing a person up. Sends a sign-in email to their work address." It also names the sibling confirm_registration as the follow-up step, so the agent can distinguish this initiation tool from the completion tool without inspecting either schema.

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

Usage Guidelines5/5

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

Explicitly states prerequisites ("Ask the person for their own work email and name first"), an exclusion rule (personal addresses such as gmail.com are refused), and the next step to take after ("then call confirm_registration"). It also tells the agent how to handle the returned link ("WITHOUT opening it"), leaving little to inference.

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.