Skip to main content
Glama

CarlNotes

Block a person

block_user
Idempotent

Block or unblock a person on CarlNotes for the connected account. A block hides each one's hot takes, chat messages, and mentions from the other. Use it when the user asks Carl or CarlNotes to block this person, unblock someone, or stop seeing someone.

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": {
      "user_id": "<user_id>",
      "is_blocked": "<is_blocked>"
    },
    "name": "block_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYesThe person's id.
is_blockedYestrue blocks the person, and false unblocks them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The description adds real context beyond the annotations by explaining the bilateral effect of a block on content visibility. The safety profile (non-destructive, idempotent) is already carried by annotations, and the description says nothing about permissions, whether existing content is removed, or how unblocking restores visibility.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose, effect, then trigger. Purpose is front-loaded and every sentence contributes distinct information with no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 full schema coverage, complete annotations, and no output schema, the description covers purpose, effect, and invocation triggers adequately. Nothing an agent needs in order to call it correctly is missing.

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% and both parameters are already documented, including the true/false polarity of is_blocked. The description's reference to blocking and unblocking mirrors the schema rather than adding format, constraint, or sourcing detail (e.g., where to obtain user_id).

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 gives a specific verb pair (block/unblock), a concrete resource (a person on CarlNotes) and the scope (the connected account). It also states the observable effect — hiding hot takes, chat messages and mentions mutually — which no sibling tool covers, so the agent can identify it without reading the schema.

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 names concrete trigger phrasing ('user asks Carl or CarlNotes to block this person, unblock someone, or stop seeing someone'), which is unusually explicit routing guidance. It stops short of stating when-not to use it or naming an alternative, though no plausible sibling overlaps.

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.