Skip to main content
Glama

Get my profile strength

getProfileStrength
Read-onlyIdempotent

The profile strength score the Home page shows: 0 to 100, a tier, and the next actions ranked by how many points each adds. A stronger profile matches better and gets introduced more, so the top action is the practical answer to "how do I get more matches". Most actions map to editPreferences or a new resume (importResumeFromLink, or getTalentDashboardLink upload_resume).

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tierYes
scoreYes
nextActionsYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavior beyond that: it discloses that Clera privately records inputs and results for usage tracking and support, and that most actions map onto specific other tools. It does not mention caching or freshness of the score, which is the main remaining unknown for a repeated-read tool.

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?

Front-loaded with what the score is and what it contains, then the value proposition, then the routing to concrete sibling tools. The privacy/usage-tracking sentence is boilerplate-ish but is real behavioral information; the 'stronger profile matches better and gets introduced more' clause is slightly padded but earns its place by explaining why the score matters.

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 inputs, full annotation coverage, and an output schema present, the description need only explain purpose, when to use it, and what to do next — all of which it does. Minor gaps: no statement of how current the score is or whether it can be stale after a profile edit.

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 for the description to disambiguate and the baseline of 4 applies. The description correctly invests its words in output meaning and follow-up routing instead of redundant input discussion.

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?

States a specific verb+resource (returns the profile strength score the Home page shows) and enumerates exactly what comes back: a 0-100 score, a tier, and ranked next actions. It is clearly differentiated from siblings like getCandidateProfile or editPreferences because it describes a computed score plus remediation actions, not profile data itself.

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 a concrete use case — the top action is the practical answer to 'how do I get more matches' — and routes follow-up work explicitly to editPreferences, importResumeFromLink, or getTalentDashboardLink (upload_resume). It stops short of stating when NOT to call it or how it relates to getCandidateProfile for raw profile inspection.

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