Skip to main content
Glama

User profile (owner-signed)

padam_profile
Read-onlyIdempotent

Return a concise, read-only profile of the person and their preferences from owner-signed records so agents can align with verified preferences at conversation start; unsigned records are excluded.

Instructions

Return the person's profile: a concise read-only summary of who the person is and what they prefer, built strictly from owner-signed identity and preference records. Call this at the start of a conversation to align with the owner's verified preferences. Unsigned records are never included.

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

Input Schema

NameRequiredDescriptionDefault
scopeNoMemory scope, e.g. 'project:code'global

Output Schema

NameRequiredDescriptionDefault
countYes
scopeYes
fencedInContentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description does add real provenance context beyond that: results come 'strictly from owner-signed identity and preference records' and 'unsigned records are never included,' which tells the agent about trust boundaries and filtering. It says nothing about pagination, size, or what happens when the scope has no signed records.

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?

Three short sentences ordered purpose → provenance → when to call, all front-loaded with no filler. 'Built strictly from owner-signed' and 'Unsigned records are never included' partially restate the same constraint, a small redundancy that keeps it from a 5.

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 values need no description, and the only parameter is fully documented in schema. The remaining minor gap is behavior when the requested scope has no signed records or is omitted entirely, which the description does not address.

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 100% and the single 'scope' parameter is documented in the schema with a default and an example, so baseline 3 applies. The description does not mention scope at all, so it adds no meaning beyond the schema, but it also has no gap to compensate for.

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 ('Return the person's profile') and immediately narrows the scope to a 'concise read-only summary of who the person is and what they prefer,' which reads as distinct from search/timeline/export siblings. It stops short of naming an alternative tool, so the differentiation is implied rather than explicit.

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 a concrete trigger: 'Call this at the start of a conversation to align with the owner's verified preferences.' That is a clear when-to-use signal. There is no when-not-to-use guidance or reference to siblings such as padam_search for deeper lookups, which keeps it below a 5.

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