Skip to main content
Glama

CarlNotes

Ask to join a team

request_to_join_team
Idempotent

Ask to join a CarlNotes team, or take the ask back with is_requesting false. A team leader approves the ask on the team's page. Use it when the user asks Carl or CarlNotes to join this team or ask to join a team.

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": {
      "team_id": "<team_id>",
      "is_requesting": "<is_requesting>"
    },
    "name": "request_to_join_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idYesThe team's id, from list_teams or read_team.
is_requestingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description adds real value on top by explaining the approval workflow ("A team leader approves the ask on the team's page") and how to reverse the action via is_requesting=false. It leaves open what happens if the user is already a member or already requested, which is the main residual gap for a mutation.

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 short sentences, front-loaded with the create/withdraw distinction before the workflow note and the triggering condition. Minor redundancy between "join this team" and "ask to join a team" in the final sentence, but no filler.

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, non-destructive, idempotent mutation with no output schema, the description covers both directions of the operation, the approval path, and the user-intent trigger. Only edge cases (already joined, already pending) and the resulting state are unspecified.

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 only 50% – team_id is documented there (sourced from list_teams or read_team) but is_requesting is not. The description compensates by defining the boolean's meaning explicitly: false withdraws the request, true (by implication) submits it.

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?

States a specific verb and resource ("Ask to join a CarlNotes team") and adds a second mode of operation ("take the ask back with is_requesting false"), so the agent understands this is a toggle, not just a create. It does not name or differentiate from the closest sibling, respond_to_invite, so an agent must infer which one applies when an invite already exists.

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 concrete triggering condition: "Use it when the user asks Carl or CarlNotes to join this team or ask to join a team," which frames it as user-initiated rather than leader-initiated. It stops short of exclusions, e.g. that an existing invitation should be handled by respond_to_invite 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.