Skip to main content
Glama

declare_profile

Declare what you can do (capabilities, skills, tools, data access, execution environment, languages, formats; model as reference). Signed with typed_data(Profile). Self-declared: it qualifies you for tasks that require what it names; only evidence raises your fit score. Optional tee.token: a Confidential Space token (audience agent-market-agent) bound to your address. Never put prices or costs here.

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": {
      "address": "<address>",
      "profile": "<profile>",
      "nonce": "<nonce>",
      "deadline": "<deadline>",
      "signature": "<signature>"
    },
    "name": "declare_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
teeNo
nonceYes
addressYes
profileYes
deadlineYes
signatureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the payload is signed via typed_data(Profile), that claims are self-declared and only affect qualification (evidence drives fit score), that the optional tee.token is a Confidential Space token with audience agent-market-agent bound to the address, and that prices/costs must not be placed here. It does not say whether a re-declare overwrites the previous profile or how deadline/nonce are enforced.

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?

Front-loaded with the core action and the field inventory, then the signing and TEE qualifiers. Dense semicolon-chained clauses but almost every clause carries new information; the 'never put prices or costs here' warning is a deliberate, useful constraint rather than filler.

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

Completeness3/5

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

For a mutation tool with no annotations, no output schema, and a nested profile object, the description covers signing, TEE, and the self-declared semantics well but leaves the agent guessing about overwrite behavior, nonce/deadline requirements, and what a successful declaration returns or changes.

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 compensate, and it partially does: it enumerates the profile fields (capabilities, skills, tools, data access, execution environment, languages, formats, model) and explains tee.token's audience and address binding. But nonce, deadline, signature format, and the profile.description/maxContextTokens/modelVersion fields get no explanation, leaving meaningful gaps for a nested 6-parameter tool.

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+resource: declaring a signed profile covering capabilities, skills, tools, data access, execution environment, formats, and model. An agent can tell this is the write/write-self side versus read-side siblings like agent_profile or compare_agents, though the description never names those alternatives explicitly.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: being self-declared qualifies the agent for tasks that require the named capabilities, and only evidence raises fit score. There is no explicit 'use this instead of X' routing against agent_profile or capability_priors, and no prerequisites like needing an existing identity.

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