usuarios

Overview Schema Source Related Servers Discussions Admin

save_profile

Saves a generated synthetic user profile as both JSON and Markdown files for machine and human consumption in a specified project directory.

Instructions

Save a generated synthetic user profile.

Saves both a JSON file (for machine consumption) and a Markdown file (for human consumption). The profile must follow the 12-dimension schema provided by get_generate_prompt.

Args: project_path: Absolute path to the project directory. profile: JSON string with the 12-dimension profile.

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

Input Schema

Name	Required	Description	Default
`project_path`	Yes
`profile`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 22, 2026

TDQS

A4/5.0

Behavior3/5

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

Description discloses the dual-file output and required schema, but does not cover overwrite behavior, error handling, or permissions. Without annotations, more detail would be beneficial, but the description is not misleading.

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?

The description is moderately concise, with key information front-loaded. The Args section is structured and clear, though some redundancy with the introductory sentences exists.

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?

The description covers purpose, output formats, and parameter details. It references the required predecessor tool. However, it lacks details on overwrite behavior or file system dependencies, which could be important given no annotations.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, the description fully compensates by providing clear descriptions for both parameters, including required format and context for profile.

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?

The description clearly states the verb 'Save', the resource 'generated synthetic user profile', and the output formats (JSON and Markdown). It also references the required schema from get_generate_prompt, distinguishing it from other save tools like save_patterns and save_validation.

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?

The description implies the tool should be used after get_generate_prompt, but does not explicitly state when to use it instead of save_patterns or save_validation. It provides some context but no explicit alternatives or exclusions.

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

Deploy Server