Compass OS: Career

add profile line

add_profile_line

Add one accomplishment line to a role in the user's profile, so resumes and the fact check can use it. Name the role by its company and title as get_profile shows them, and add only something the user said is true. Use update_profile to reword or replace a role's accomplishments, and log_win for a dated win. It asks the user first and only appends: the same line sent twice is added twice. A role that isn't in the profile comes back as a miss. Once it's saved, undo can put it back within 24 hours.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>",
      "title": "<title>",
      "line": "<line>"
    },
    "name": "add_profile_line"
  }
}

Input Schema

Name	Required	Description
`line`	Yes	The accomplishment, one line in the user's words, e.g. "Led the checkout redesign that lifted conversion 12%"
`title`	Yes	The role's title, exactly as get_profile shows it
`company`	Yes	The role's company, exactly as get_profile shows it

Output Schema

Name	Required	Description
`text`	Yes	The answer, or what was done, in plain words for the user: the same text as content
`undo`	No	On a saved write: its undo handle, for undo within 24 hours
`widget`	No	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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / company / description

Previous value: -"The role's company, exactly as profile_gaps shows it"New value: +"The role's company, exactly as get_profile shows it"

changedInput schema / properties / title / description

Previous value: -"The role's title, exactly as profile_gaps shows it"New value: +"The role's title, exactly as get_profile shows it"

Changed1 schema field changedNov 5, 2026

addedOutput schema / properties / undo

Added value: +{
+  "description": "On a saved write: its undo handle, for undo within 24 hours",
+  "type": "string"
+}

Changed4 schema fields changedNov 4, 2026

addedInput schema / properties / company / description

Added value: +"The role's company, exactly as profile_gaps shows it"

addedInput schema / properties / line / description

Added value: +"The accomplishment, one line in the user's words, e.g. \"Led the checkout redesign that lifted conversion 12%\""

addedInput schema / properties / title / description

Added value: +"The role's title, exactly as profile_gaps shows it"

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

First observedNov 4, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Beyond the annotations, it discloses several non-obvious behaviors: it asks the user first, it is append-only, duplicate lines are added twice (consistent with idempotentHint=false rather than contradicting it), an unknown role returns a miss, and undo can revert within 24 hours. Only authentication/permission requirements and response shape are left uncovered, and the latter is partly handled by the output schema.

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?

Four tight sentences, front-loaded with purpose and followed by differentiation, then behavioral caveats in order of risk. Every sentence carries information an agent needs; nothing is repeated from the schema verbatim in a wasteful way.

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-required-parameter append-only mutation with annotations and an output schema, this covers purpose, alternatives, input provenance, duplicate risk, failure mode, and reversibility. Nothing an agent needs to invoke 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 baseline is 3, but the description adds real constraint beyond the schema: the line must be something the user actually asserted as true, and company/title must match get_profile's rendering exactly rather than being free-form. Those are usage rules the schema fields alone don't convey.

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 opens with a specific verb+resource ('Add one accomplishment line to a role in the user's profile') and states the downstream purpose (resumes and fact check). It distinguishes itself from update_profile and log_win by naming both explicitly, so an agent can route correctly without opening another 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?

It gives explicit alternatives with the condition that selects them: update_profile to reword or replace, log_win for a dated win. It also states positive preconditions (name the role as get_profile shows it, only add something the user said is true), which is unusually complete guidance.

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 tools Inspect

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

Need Help?