get_my_profileRetrieves the authenticated user's Freelancehunt profile, including rating, skill rankings, verification status, Plus membership, and completed project counts.
The authenticated account: rating, per-skill ranking positions, Plus status, verification state and completed-project counters.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnlyHint and openWorldHint, so the safety profile is established. The description adds useful context about the returned fields, but it does not disclose additional behavioral traits such as authentication requirements or failure modes. With annotations present, the extra field detail earns a solid mid-range score.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, compact sentence with no filler. It front-loads the key scoping information ('authenticated account') and then lists the specific data elements, making every word informative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters, no output schema, and a simple read-only profile lookup, the description fully covers what the agent needs to know: which account is involved and what fields will be returned. Nothing essential is missing for correct selection and invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description adds meaningful implicit context by clarifying that the profile belongs to the authenticated account, which effectively explains the implicit authentication context without needing input parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The title and description clearly identify the tool as returning the current authenticated user's profile, and the description lists the specific data fields returned. It differentiates from list_profiles and get_freelancer by scoping to the authenticated account, though it does not explicitly name a verb like 'retrieves.'
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'the authenticated account' provides clear context for when to use this tool: when the agent needs the current user's own profile rather than another user's or a general profile list. It does not explicitly exclude sibling tools, but the self-scoping is sufficient for the zero-parameter context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.