Skip to main content
Glama
Sign In
usuarios

usuarios

by Sebtiago
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_generate_prompt

Generates a prompt from research patterns to define a 12-dimension profile schema for creating synthetic user profiles. Accepts project path and optional profile count.

Instructions

Generate a prompt for creating synthetic user profiles.

Reads the patterns file and returns a prompt with the complete 12-dimension profile schema for you to generate rich synthetic user profiles.

Args: project_path: Absolute path to the project directory. count: Optional number of profiles to generate (default: auto-detect from patterns).

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>"
    },
    "name": "get_generate_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathYes
countNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool 'reads the patterns file' and 'returns a prompt', but does not mention side effects, auth requirements, or file existence assumptions. Missing information on whether it modifies state or has rate limits.

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 concise with three brief sections: a purpose summary, a process explanation, and parameter details. It is front-loaded with the core purpose. However, the Args section partially duplicates schema information, slightly reducing conciseness.

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?

The description sufficiently explains the tool's function and parameters, and since an output schema exists, return value explanation is not needed. However, it lacks context about prerequisites (e.g., existence of patterns file) and fails to provide usage guidance or behavioral notes, leaving gaps for the agent.

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

Parameters4/5

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

The description adds meaningful semantics beyond the bare schema: 'project_path' is described as 'Absolute path to the project directory' and 'count' as 'Optional number of profiles to generate (default: auto-detect from patterns)'. Schema coverage is 0%, so the description effectively compensates.

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?

The description clearly states the tool generates a prompt for synthetic user profiles by reading a patterns file. It specifies the output includes a complete 12-dimension profile schema. While the purpose is specific and includes a verb and resource, it does not explicitly differentiate from sibling tools like 'get_profile' or 'get_research_prompt', which could cause ambiguity.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus the siblings. It does not mention prerequisites, alternative tools, or scenarios where this tool is inappropriate. The agent is left without context for selection.

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

Deploy Server

Other Tools