Skip to main content
Glama

get_profile

Retrieve your saved job seeker profile to review stored skills, experience, and preferences before tailoring resumes or applying to jobs.

Instructions

Retrieve your saved job seeker 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.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. "Retrieve" hints at a non-mutating read, but the definition says nothing about what happens if no profile has been saved, whether the result includes all saved fields, or the response shape. For a tool with zero annotation coverage this is a notable gap, though the operation is inherently simple.

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?

A single six-word sentence with the resource front-loaded and no filler. It is appropriately sized for a trivial read, though it is thin enough that a clause on return contents would have earned its place.

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?

For a zero-parameter read tool with no output schema, the agent still lacks any statement of what the profile contains or how absence is signaled. Annotations are absent too, so nothing else fills that gap. It is minimally adequate but not complete.

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 no parameters, so there is nothing for the description to clarify beyond the schema's empty object. Baseline 4 applies; the description correctly avoids inventing inputs like a user ID.

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?

"Retrieve your saved job seeker profile" states a specific verb (retrieve) and resource (job seeker profile), making the read nature obvious. It implicitly contrasts with the sibling save_profile, but never names it or any other alternative, so differentiation relies on the agent inferring it from the sibling list.

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?

Usage is only implied: an agent can guess this is the tool to call when it needs the user's stored profile data. There is no explicit when-to-use statement, no prerequisite (e.g. profile must already exist), and no routing away from save_profile for the write case.

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