Skip to main content
Glama

Agent profile

agent_profile
Idempotent

Sets your label, operator and contact, shown to Wave admins. Overwrites only the fields you send; leaves the others as they are. Returns the saved profile. Free. Needs sign-in (auth_challenge then auth_verify).

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

Input Schema

NameRequiredDescriptionDefault
labelNoYour agent's name, up to 60 characters
contactNoEmail or https URL, up to 200 characters
operatorNoWho runs the agent, up to 80 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / contact / description
      Previous value: -"Email or https URL"New value: +"Email or https URL, up to 200 characters"
    • addedInput schema / properties / contact / maxLength
      Added value: +200
    • addedInput schema / properties / label / description
      Added value: +"Your agent's name, up to 60 characters"
    • addedInput schema / properties / operator / description
      Added value: +"Who runs the agent, up to 80 characters"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real value beyond them: partial-update merge semantics ('Overwrites only the fields you send; leaves the others as they are'), the return value ('Returns the saved profile'), and that the call is free.

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?

Five short sentences, front-loaded with purpose, then merge semantics, return value, cost, and auth. Every sentence carries distinct information and nothing is repeated.

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 three-optional-parameter, non-destructive writer with no output schema, the description covers what it writes, how partial updates behave, what it returns, cost, and the auth prerequisite. 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%, with maxLength and field descriptions already documented per parameter. The description restates the same three field names but adds no format or validation detail beyond the schema, so baseline 3 applies.

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?

Specific verb and resource: 'Sets your label, operator and contact, shown to Wave admins.' It names the exact fields written and the audience, so an agent can distinguish this profile-setting tool from auth and wallet siblings without opening 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?

Explicitly states the prerequisite flow ('Needs sign-in (auth_challenge then auth_verify)') and names the sibling tools to call first, which is strong routing guidance. It does not give a when-not-to-use condition, but for a simple profile setter there is little ambiguity.

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