Skip to main content
Glama
Sign In

Compass OS: Career

by dev.compass-os
OverviewDiscussionsAdmin

get profile

get_profile
Read-onlyIdempotent

Read the user's profile, the source every resume and fact check uses: all of it, one section (headline, summary, experience, skills, education), or one role by company and title with its numbered accomplishments and how it connects to the role before it. Section gaps shows the profile at a glance (name, title, summary, up to six roles with their accomplishments) and which profile sections aren't ready to build resumes from yet, each with what it needs: use it to find gaps, or before add_profile_line so a line isn't repeated. Read the part before changing it with update_profile or link_roles; for a resume's text use get_material. Read-only. An unknown role comes back as a miss listing the roles.

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

Input Schema

NameRequiredDescriptionDefault
titleNoWith company, read just this role: its title
companyNoWith title, read just this role: its company
sectionNoThe section to read; leave empty for all of it; gaps for the profile at a glance and the sections not ready to build resumes from yet

Output Schema

NameRequiredDescriptionDefault
textYesThe answer, or what was done, in plain words for the user: the same text as content
undoNoOn a saved write: its undo handle, for undo within 24 hours
widgetNoThe card the host draws with it, e.g. "pipeline"; "confirm" means a write waits for the user's Yes and nothing is saved yet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / section / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "all",
-      "headline",
-      "summary",
-      "experience",
-      "skills",
-      "education"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "all",
+      "headline",
+      "summary",
+      "experience",
+      "skills",
+      "education",
+      "gaps"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / section / description
      Previous value: -"The section to read; leave empty for all of it"New value: +"The section to read; leave empty for all of it; gaps for the profile at a glance and the sections not ready to build resumes from yet"
  2. Changed1 schema field changed
    • addedOutput schema / properties / undo
      Added value: +{
+  "description": "On a saved write: its undo handle, for undo within 24 hours",
+  "type": "string"
+}
  3. Changed4 schema fields changed
    • addedInput schema / properties / company / description
      Added value: +"With title, read just this role: its company"
    • addedInput schema / properties / section / description
      Added value: +"The section to read; leave empty for all of it"
    • addedInput schema / properties / title / description
      Added value: +"With company, read just this role: its title"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "text": {
+      "description": "The answer, or what was done, in plain words for the user: the same text as content",
+      "type": "string"
+    },
+    "widget": {
+      "description": "The card the host draws with it, e.g. \"pipeline\"; \"confirm\" means a write waits for the user's Yes and nothing is saved yet",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered; the description's 'Read-only' restates that but adds real behavior beyond it. The miss behavior ('an unknown role comes back as a miss listing the roles') and the contents of each read mode are genuinely useful operational context, though the description doesn't discuss pagination or limits on the all-mode read.

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?

Purpose is front-loaded and every clause carries information, but the single dense paragraph strings together modes, caveats and alternatives with semicolons, making it harder to scan than a short structured list. 'Read-only' duplicates the readOnlyHint annotation and could be dropped without loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with full schema coverage, an output schema and read-only annotations, the description covers everything an agent needs: all read modes, what each returns, the unknown-role fallback, and the sibling to use for a different need. Nothing required to call it correctly is missing.

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?

Schema coverage is 100%, so the schema already documents title, company and the section enum, establishing a baseline of 3. The description adds meaning on top: it explains how title and company combine to select a single role, and expands on what the 'gaps' enum value actually returns (name, title, summary, up to six roles plus which sections aren't resume-ready and what each needs).

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 opening sentence gives a specific verb (read) and resource (the user's profile) plus its role as the source of truth for resumes and fact checks, then enumerates the three read modes: everything, one section, or one role by company and title. It also distinguishes itself from get_material for resume text, so an agent can separate it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance is given for the gaps mode ('use it to find gaps, or before add_profile_line so a line isn't repeated') and for the read-before-write pattern ('read the part before changing it with update_profile or link_roles'). It also names the alternative for a different need ('for a resume's text use get_material'), covering both routing directions.

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

All Compass OS: Career toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources