Skip to main content
Glama

get_profile

Read-only

Read the signed-in Linkdfolio profile (work, education, and contact facts). Returns those facts at the top level, plus preferences, siteLink, version, and appUrl. siteLink is the person's Linkdfolio website: { url, state }, where state is live, building, or none, and url is set only when live. It is read-only and managed in the app. preferences.siteLinkInDocuments says whether new resumes and cover letters get that website in their header. preferences.targetRoles and preferences.situation, when set, are the roles the person is going for and their career situation: light guidance for choosing resume entries, never wording. Call this before update_profile.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so the description's 'It is read-only and managed in the app' adds little on the safety axis. However, with no output schema, the description does real work by laying out the return shape (top-level facts plus preferences, siteLink, version, appUrl), the siteLink state machine (live/building/none, url set only when live), and the intended interpretation of preferences.targetRoles as guidance for entry selection, not wording.

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 opening sentence carries purpose and return contents, and the siteLink/preferences explanations follow in logical order. It is dense but tightly written; the stray mention of version and appUrl is the only filler.

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?

For a no-argument read tool with no output schema, the description covers what comes back and how key fields should be interpreted, which is what an agent needs before calling update_profile. Edge cases such as calling before sign-in are not addressed, but nothing essential to correct invocation is missing.

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 tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate; baseline is 4. The description correctly avoids wasting space on parameter detail.

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 opens with a specific verb and resource ('Read the signed-in Linkdfolio profile') and enumerates the content (work, education, contact facts). It is immediately distinguishable from the mutating sibling update_profile, which it also names.

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?

It gives explicit sequencing guidance: 'Call this before update_profile', which tells the agent when to reach for it. It does not state when not to call it or name non-profile alternatives, but the read-vs-write split with update_profile covers the main decision.

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.

Resources