Skip to main content
Glama

Preview profile

preview_profile
Read-only

Validate an authorized portable profile draft and private context labels without enrolling or publishing. No raw memory or private conversations.

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": {
      "profile": "<profile>"
    },
    "name": "preview_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNo
profileYes
referralCodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / referralCode / maxLength
      Added value: +100
    • changedInput schema / properties / referralCode / pattern
      Previous value: -"^[a-f0-9]{24}$"New value: +"^[\\p{L}\\p{N}]+(?:-[\\p{L}\\p{N}]+)*$"
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, but the description adds the non-obvious privacy guarantee ('no raw memory or private conversations'), which tells the agent what is guaranteed not to leak into the validation. It stops short of saying what a validation returns or whether it emits errors versus warnings.

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?

Two short, front-loaded sentences with no wasted clauses. The phrasing 'authorized portable profile draft' leans on jargon that costs some clarity, but the structure is efficient.

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 tool with a large nested schema, no parameter descriptions, and no output schema, the description should carry much more. It never explains what the validation produces (field errors? a preview card?) or what 'authorized' requires, so an agent cannot predict the result of a call.

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% across a deeply nested three-parameter schema with dozens of fields. The description only hints that context carries 'private context labels'; it says nothing about the required profile fields (name, headline, offers, needs), the referralCode, or the inferredFields/sourceLabels semantics that the schema leaves undocumented.

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?

Clear verb+resource: validates a profile draft plus context labels, and states the boundary that nothing is enrolled or published. It does not name or distinguish itself from siblings like prepare_signup or assess_profile_context, so an agent must infer the split from the word 'validate'.

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?

'Without enrolling or publishing' implies this is the dry-run that precedes prepare_signup, but that is never stated explicitly and no alternative is named. The agent is left to infer when preview ends and signup begins.

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.