Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

Read my Jobiba profile

get_my_profile
Read-onlyIdempotent

Read the authenticated candidate profile using only career facts needed for job workflows.

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_my_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
idYes
nameNo
emailNo
nicknameNo
careerProfileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a safe, idempotent, closed-world read, so the safety profile needs no restating. The description does add one real behavioral detail beyond them — that the response is scoped to career facts relevant to job workflows rather than the full profile — but it never says what is filtered out, leaving the agent unable to predict the payload.

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 sentence with the verb and resource front-loaded and no filler. The trailing qualifier is compact but slightly ambiguous, costing it a point against a fully crisp statement.

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?

With no inputs and an output schema handling return-value documentation, the description only needs to establish scope and safety, which it largely does. The remaining gap is routing guidance against the profile-related siblings, which would help but is not essential for correct invocation.

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 with 100% schema coverage, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing parameter talk.

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 names a specific verb ("Read") and resource ("the authenticated candidate profile"), which cleanly distinguishes it from the obvious sibling update_my_profile by the read/write axis. It stops short of naming that alternative explicitly, and the trailing clause about "career facts needed for job workflows" blurs rather than sharpens the scope.

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: the phrase "needed for job workflows" hints at the context in which an agent should call it, and "authenticated" signals it operates on the current user with no arguments. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as update_my_profile or profile_strength.

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.