Skip to main content
Glama

CarlNotes

Answer an invite

respond_to_invite
Idempotent

Accept or decline a CarlNotes team or topic invite waiting for you, by the invite id read_activity lists. Accepting a team invite joins the team, or asks to join it if a member sent an open link. Use it when the user asks Carl or CarlNotes to accept an invite, decline an invite, or join the team I was invited to.

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": {
      "invite_id": "<invite_id>",
      "is_accepted": "<is_accepted>"
    },
    "name": "respond_to_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_idYes
is_acceptedYes

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?

The annotations declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, and the description adds real behavior beyond them: accepting a team invite actually joins the team, or becomes a join request for open-link invites. It still lacks detail about what declining does and what the call returns, but the side-effect semantics of the main branch are disclosed.

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 sentences, both front-loaded, with the action first and invocation guidance second. Slightly dense with repeated 'invite' phrasing, but nothing is wasted and no filler is present.

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?

With only two parameters, no output schema, and an otherwise bare schema, the description covers the essentials: where to get the id and what accepting means. It omits the effect of declining and the call's response or error behavior, which keeps it from being fully complete.

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 0%, so the description must compensate for the two parameters. It explains the provenance of invite_id ('the invite id read_activity lists') and implicitly maps is_accepted to accept versus decline, but it never names or explicitly defines the boolean parameter's true/false meaning.

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 sentence 'Accept or decline a CarlNotes team or topic invite waiting for you' gives a specific verb pair, the resource, and the scope (pending invites). It also names read_activity as the source of invite ids, which distinguishes it from send_invite and request_to_join_team.

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?

The description explicitly lists triggering user intents: accept an invite, decline an invite, or join the team I was invited to. It also explains the branch condition for open links ('asks to join it if a member sent an open link'), routing that case correctly instead of leaving it to inference. It does not state when not to use the tool, such as when the user has no pending invite, so it falls short of 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.