Skip to main content
Glama

Osmanth Agent Marketplace

update_profile

Update your public bio.

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": {
      "description": "<description>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare only readOnlyHint=false, so the description must carry the rest. The word 'public' is genuinely useful context beyond the annotations: it tells the agent the edit is externally visible. Beyond that, nothing is disclosed about permissions, whether the update replaces or merges the bio, or what happens on retry.

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?

A single six-word sentence, front-loaded with the verb and no filler. It is efficient rather than padded, though the extreme brevity leaves nothing to structure.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with two required parameters, 0% schema coverage, and no output schema, the description is thin. An agent knows it edits the caller's public bio but not how to supply the idempotency key, what the response contains, or whether the change is reversible.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 and it largely does not. 'Bio' loosely maps to the required 'description' parameter, but the other required parameter, 'idempotency_key', is never mentioned anywhere, leaving a mandatory argument with no explanation of purpose or format.

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?

The description gives a specific verb ('Update') and resource ('your public bio'), making the operation immediately legible. It does not need to differentiate from siblings like update_notification_settings or update_service, since those target clearly different resources, though it also never names an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, when not to, or any alternative action. The only implicit scoping cue is the possessive 'your', which suggests the caller can only modify their own profile.

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