Skip to main content
Glama

Update my profile

bb_update_profile
Idempotent

Updates editable Blackboard profile fields (e.g., title, name, email) when write access is enabled and confirmation is provided.

Instructions

Update editable profile fields. Blackboard only permits fields flagged in editableFields (often just title). Requires BB_ALLOW_WRITES=1 and confirm:true.

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

Input Schema

NameRequiredDescriptionDefault
titleNo
confirmNo
givenNameNo
familyNameNo
emailAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: a server-side editability restriction (often only title is writable) and two hard gating requirements (BB_ALLOW_WRITES=1 and confirm:true). It does not say whether non-editable fields are rejected or silently ignored, which is the main remaining 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.

Conciseness5/5

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

Two short sentences, zero filler, with the editability caveat and the write-gate requirements front-loaded before the agent ever inspects the schema.

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 mutation tool with annotations and no output schema, the definition covers the safety gates and the editability constraint that would otherwise cause silent failures. Only the outcome of supplying a non-editable field and the shape of a successful response remain unstated.

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 carry parameter meaning. It explains the confirm gate and warns that title/givenName/familyName/emailAddress may not all be editable, but it does not distinguish which parameters are actually honored versus ignored, leaving several of the five parameters semantically thin.

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 ('Update editable profile fields'), making clear it mutates the caller's own profile and is the write counterpart to the read profile tool. It does not explicitly name a sibling, but the verb/resource pairing leaves little ambiguity.

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 concrete preconditions for use: fields must be flagged in editableFields, BB_ALLOW_WRITES=1 must be set, and confirm:true must be passed. It lacks an explicit 'use X instead when...' routing statement, but the context for when this tool applies is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.