Skip to main content
Glama

searchnapply

Get my profile

profile_get
Read-onlyIdempotent

Purpose: Read the user's profile, section by section, with the rules for a tailored resume or cover letter; an empty section is unfilled. When: Before you tailor a resume or cover letter, or when the user asks what their profile holds. Cost: About 1410 tokens for a filled 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": "profile_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
messageNoPresent when the profile is empty: where the user fills it in.
profileYesThe profile document, section by section, as searchnapply stores it.
resumeRulesYesThe rules to follow when writing a tailored resume or cover letter, one rule per line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds useful context the annotations lack: the response is organized section by section, empty sections indicate unfilled data, and the call costs roughly 1410 tokens for a filled profile, which lets an agent budget context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three labeled lines (Purpose, When, Cost) front-load the essentials with no filler. Every line carries information an agent would otherwise have to guess.

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?

An output schema exists, so return values need no explanation, and the description still flags the token cost and the empty-section semantics. What is missing is minor: whether the full profile can be empty and whether permissions are required.

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, so there is nothing to disambiguate and the baseline is 4. The description correctly implies a no-argument call.

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?

States a specific verb and resource ("Read the user's profile") and adds scope detail: it returns the profile section by section with the rules needed for tailoring, and empty sections mean unfilled. The read verb implicitly separates it from the profile_update sibling, though it never names that alternative.

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?

Gives an explicit when: before tailoring a resume or cover letter, or when the user asks what their profile holds. It does not state when not to use it or name profile_update as the tool for writing, so the exclusion is only implied by the verb.

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