Skip to main content
Glama
remoet-labs

remoet

Official
by remoet-labs
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

View Profile

get_profile
Read-only

Retrieve your full Remoet profile to assess and improve your professional presence. Use this to uncover gaps in summary, projects, work history, and basics for job search optimization.

Instructions

Get the user's full Remoet profile. IMPORTANT: Always call this first before making any changes.

PROFILE GAP ANALYSIS: After fetching, run a full evaluation and proactively surface findings ranked by impact. Offer to fix each issue on the spot. Be encouraging, not critical — "Your profile has a solid foundation, here are a few things that could make it stand out."

CHECK 1 — SUMMARY & DISCOVERABILITY (highest impact):

  • Summary empty or weak? Under 100 chars, no tech stack mentioned, no years of experience, or no differentiator = needs rewriting. See update_profile for guidance. This is the first thing companies read.

  • Call get_visibility. If NONE, suggest STARRED — creates a two-way match where starred companies can discover the user.

  • Check get_starred_listings. Zero stars = empty job feed. Help them find and star companies matching their tech stack.

  • Cross-reference starred companies' tech stacks against the user's skills. Flag mismatches that add noise.

CHECK 2 — PROJECTS (what makes them special?):

  • Zero projects = #1 gap for junior/mid developers. Projects differentiate candidates with similar job histories. Ask about side projects, open source, personal apps, hackathons, scripts, blogs.

  • Projects without URLs or descriptions are barely better than no projects.

CHECK 3 — WORK HISTORY (can they do this?):

  • Zero jobs = critical gap. Walk user through adding experience or importing from CV.

  • Jobs without descriptions = missed opportunity. Each role should explain what was built, what tech was used, and what impact it had.

  • Descriptions without measurable impact? Push for specifics: users served, performance gains, revenue impact, team size. "Built React frontend" → "Built React frontend serving 50K monthly users, reducing load time by 40%."

  • Technologies array empty on jobs with tech in the description? Ask to add them — they feed into job matching.

  • Remote experience not highlighted? If they've worked remotely, ensure isRemote: true — remote hiring managers look for proof.

CHECK 4 — BASICS (will they even look?):

  • Avatar missing? Profiles without photos get less engagement.

  • Location vague? "Europe" is too broad. Companies need timezone and jurisdiction. "Lund, Sweden" is specific.

  • GitHub/LinkedIn missing? Table stakes for developers.

CHECK 5 — EDUCATION:

  • Empty education? Ask about degrees, bootcamps, certifications, notable courses.

If the user shares a CV, resume, or website, populate their entire profile (update_profile, create_work_experience, create_project, create_education), then search and star matching companies, and finally surface relevant jobs — all in one go.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds no contradiction. It clarifies that the tool returns the profile and implies no side effects, but does not elaborate on return format or pagination. The additional gap analysis instructions are about agent behavior, not tool behavior.

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

Conciseness2/5

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

The description is excessively long with large blocks of procedural instructions for the agent (checks 1-5) that are not essential for understanding the tool itself. The first sentence is concise, but the rest is verbose and could be condensed.

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?

Given zero parameters, no output schema, and annotations covering read-only, the basics are covered. However, the description includes extensive workflow instructions that go beyond the tool's function, making it feel over-specified but not necessarily more complete for selecting/invoking the tool.

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 has no parameters, and schema description coverage is 100%. Per guidelines, baseline is 4. The description adds no parameter meaning because none exist.

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?

The description clearly states 'Get the user's full Remoet profile' with a specific verb and resource. It distinguishes from sibling tools like get_projects or get_education by specifying the exact object (profile). The instruction to call this first adds context.

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?

Explicitly says 'Always call this first before making any changes,' providing clear when-to-use guidance. However, it does not mention when not to use or compare to alternatives like other 'get' tools, which keeps it from a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/remoet-labs/remoet-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server