Skip to main content
Glama

CarlNotes

Invite someone

send_invite

Invite a person to a CarlNotes team you belong to, or to a topic you edit, by their username or their email address. An email invite sends an email and counts toward a daily limit. Use it when the user asks Carl or CarlNotes to invite someone, invite a friend to my team, or share this topic with a person.

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": "send_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe person's email address, in place of username.
team_idNoThe team to invite to, in place of topic_id.
topic_idNoThe topic's id. Optional on a topic-bound server, which already knows its topic.
usernameNoThe person's CarlNotes username.

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?

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses two things the schema does not: an email invite actually sends mail and counts against a daily limit, and the inviter must belong to the team or edit the topic. It does not say what happens on success or how a failed/duplicate invite is reported, leaving a small 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 sentences, front-loaded with the action and target, then the email/limit caveat, then the invocation triggers. The final sentence's example phrases are somewhat listy but still serve as useful matching cues, so little 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 4-parameter, non-destructive mutation with no output schema and full schema descriptions, the definition covers who can be invited, how they are identified, the target scope, and the email side effect. What is missing is only the return value and duplicate-invite behavior, which is minor here.

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%, including the 'in place of topic_id' relationship between team_id and topic_id, so the baseline is 3. The description restates the username-or-email choice and the team-or-topic target but adds no new syntax, format, or precedence rules 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?

The description names a specific verb and resource (invite a person to a team or a topic) and states the two identifying methods (username or email). It also scopes the action to teams you belong to and topics you edit, which distinguishes it from respond_to_invite, the sibling that handles the receiving side.

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 explicit trigger phrasing ('when the user asks Carl or CarlNotes to invite someone, invite a friend to my team, or share this topic with a person'), so an agent can pattern-match a request. It lacks any when-not guidance or a named alternative for the respond/receive case, keeping it below a 5.

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.