Skip to main content
Glama

Register a company

register_company

Registers a company's interest in Datari Labs' free referral service. Requires the person's explicit consent and their work email. After registering, the company completes the normal sign-up (fit check, account and interview) on the Datari Labs website; a confirmation email with the link is sent to the work email given. Never register anyone who has not clearly said yes.

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": {
      "company_name": "<company_name>",
      "work_email": "<work_email>",
      "website": "<website>",
      "consent": "<consent>"
    },
    "name": "register_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
consentYesMust be true. Confirms the person asked Datari Labs to register the company and agreed to be contacted by email about it.
websiteYesCompany website, e.g. https://example.com
work_emailYesA work email at the company's own domain
company_nameYesRegistered or trading name of the company
contact_nameNoOptional: name of the person registering

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-destructive write, and the description adds real context beyond them: a confirmation email is sent to the given work email, and the rest of the process happens off-tool. It does not address what happens on duplicate registration despite idempotentHint=false, which is the one behavioral gap.

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 tight sentences, front-loaded with what the tool does, then the prerequisites, then the safety rule. The closing 'never register anyone who has not clearly said yes' partly restates the consent requirement, but it earns its place as a hard guardrail.

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 five-parameter write tool with no output schema, the description covers prerequisites, side effects (email), and the post-registration path. Only duplicate-registration behavior is unaddressed, a minor gap given otherwise full annotation and schema coverage.

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 coverage is 100%, so every parameter including the consent boolean is already documented. The description reinforces why consent matters and that the work email is the destination for the confirmation link, but adds no format or validation detail beyond the schema.

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?

States a specific verb and resource ('Registers a company's interest') and immediately narrows scope: this is a referral-service registration, not the full sign-up, which happens later on the website via fit check, account and interview. That delineation separates it from a sibling like check_fit without naming it.

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?

Gives a clear precondition (explicit consent and a work email) and an explicit prohibition ('Never register anyone who has not clearly said yes'). It also explains the downstream flow, implying this tool is only the first step, but it does not name an alternative tool or say when a caller should check status instead.

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