Skip to main content
Glama

searchnapply

Update my profile

profile_update
DestructiveIdempotent

Purpose: Replace whole sections of the user's profile with what the user asked to change. When: The user asks to add, fix or remove something in their profile, not on your own initiative. Cost: About 1410 tokens for the profile that comes back.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sections": {
        "summary": {
          "text": "Backend engineer with ten years of distributed systems work."
        }
      }
    },
    "name": "profile_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionsYesThe profile sections to replace, each in the shape profile_get returns it.

Output Schema

NameRequiredDescriptionDefault
changedYesThe sections that were written.
profileYesThe profile document as searchnapply stores it after the writes.

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 flag destructiveHint and idempotentHint, so the safety bar is lower. The description still adds real value beyond them: 'replace whole sections' tells the agent this is not a merge, and the ~1410-token return cost is a behavioral fact the schema never conveys. It could go further and state explicitly that omitted entries inside a supplied section are dropped.

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 labeled lines, front-loaded by purpose, then condition, then cost. No sentence is redundant and the most decision-relevant constraint comes first.

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?

An output schema exists, so return shape needn't be explained, and the description covers the trigger, the replace semantics and the token cost. The one remaining gap is an explicit warning about data loss for entries omitted within a replaced section, which matters for a destructive write tool.

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 the schema already says sections are 'replaced' in the shape profile_get returns them. The description reinforces the wholesale-replacement semantic, which is useful, but adds no per-section or id-handling detail beyond what the schema documents.

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 scope: 'Replace whole sections of the user's profile with what the user asked to change.' That distinguishes it from a partial patch and from the read-side sibling profile_get, though the sibling is never named explicitly.

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 'When' line gives a concrete trigger (user asks to add, fix or remove something in their profile) plus an explicit when-not (not on your own initiative). It stops short of naming profile_get as the required prerequisite for obtaining entry ids, but the usage condition is unambiguous.

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.

Resources