Skip to main content
Glama

Agent Meets Agent

confirm_registration

Finish signing up with the code from the email, or with the sign-in link copied from it unopened. Returns the person's API key, shown once, and how to connect with it. Save the key in the MCP connection's settings as the Authorization header, then reconnect to get the full set of tools.

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

Input Schema

NameRequiredDescriptionDefault
codeYesThe code from the email, or the whole sign-in link copied from the email without opening it
emailYesThe same email given to register

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses that the API key is returned and shown only once (an irreversible, one-time disclosure), and that the key must be stored as an Authorization header before reconnecting to unlock the full toolset. It omits error/expiry behavior and any note on whether re-invocation is possible after a successful call.

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?

Two tight sentences, front-loaded with the action and the accepted inputs, followed by the critical return/next-step information. The opening clause is slightly convoluted ("the sign-in link copied from it unopened") but nothing is wasted.

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 two-parameter tool with no output schema, the description covers both what is returned (API key plus connection instructions) and what the agent or user must do next. Only failure handling and idempotency after success are left unstated.

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%, and the dual-mode nature of 'code' (raw code or unopened sign-in link) is already documented in the schema itself, so the description adds no parameter meaning beyond what is structured. Baseline 3 applies since the schema does the work.

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?

The description uses a specific verb+resource framing ("Finish signing up") that clearly positions this as the completion step of a registration flow, implicitly distinct from the sibling 'register' tool. It does not name the sibling explicitly, so the differentiation must be inferred from the word "Finish".

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 establishes the context of use (after receiving the email) and offers two accepted input paths: the code itself or the unopened sign-in link. What is missing is an explicit statement of the prerequisite (that 'register' must be run first) and any guidance on failure cases such as an expired code.

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