Skip to main content
Glama

Jobiba Jobs: Job Search, Salary, CV & Apply

How strong is my profile?

profile_strength
Read-onlyIdempotent

Scores the candidate profile out of 100 across 13 sections, lists the next improvements with points to gain, and reports whether recruiters can currently find the 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_strength"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing the returned content (a numeric score over 13 sections, ranked improvements with point values, recruiter-visibility status) — important since there is no output schema. It says nothing about cost/latency of the scoring pass or behavior when the profile is empty.

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?

A single sentence with the primary output (the score) front-loaded, followed by the two secondary outputs. No filler, no restatement of the title.

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 zero parameters and no output schema, the description carries the burden of describing return values, and it does so specifically (100-point scale, 13 sections, points-to-gain, recruiter visibility). The remaining gap is edge-case behavior — empty/incomplete profiles and whether the scoring call is expensive — which an agent would want to know before invoking.

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 disambiguate; baseline applies. No scope parameters (e.g., limiting to certain sections) are advertised, consistent with the empty schema.

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?

Concrete verb+resource ("Scores the candidate profile") plus the exact shape of the result: a 0-100 score across 13 sections, improvement points, and recruiter discoverability. It does not distinguish itself from the overlapping profile_optimizer or skill_gap_analysis siblings, which also promise improvement suggestions.

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 description frames the tool as a diagnostic check-up on the candidate's profile, so an agent can infer 'call this to assess the profile'. There is no explicit when-to-use, no prerequisite (e.g., profile must already contain items), and no statement about when to prefer profile_optimizer instead.

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.