my_cvThe person's own Profile & CV: headline, about, experience, education, skills, languages, links, who sees it. Read it before update_my_cv.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"Output schema / (root)Previous value: -{
- "$schema": "http://json-schema.org/draft-07/schema#",
- "additionalProperties": false,
- "properties": {
- "counts": {
- "anyOf": [
- {
- "additionalProperties": false,
- "properties": {
- "both": {
- "$ref": "#/properties/counts/anyOf/0/properties/friends"
- },
- "friends": {
- "type": [
- "number",
- "string"
- ]
- },
- "pro": {
- "$ref": "#/properties/counts/anyOf/0/properties/friends"
- }
- },
- "required": [
- "friends",
- "pro",
- "both"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
- ]
- },
- "handle": {
- "type": [
- "string",
- "null"
- ]
- },
- "none": {
- "type": "boolean"
- },
- "note": {
- "type": "string"
- },
- "profile": {
- "additionalProperties": false,
- "properties": {
- "about": {
- "type": "string"
- },
- "city": {
- "type": "string"
- },
- "education": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "description": {
- "$ref": "#/properties/profile/properties/experience/items/properties/description"
- },
- "from": {
- "$ref": "#/properties/profile/properties/experience/items/properties/from"
- },
- "id": {
- "type": "string"
- },
- "programme": {
- "type": "string"
- },
- "school": {
- "type": "string"
- },
- "to": {
- "$ref": "#/properties/profile/properties/experience/items/properties/to"
- }
- },
- "required": [
- "id",
- "school",
- "programme",
- "from",
- "to",
- "description"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "experience": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "description": {
- "type": "string"
- },
- "from": {
- "type": "string"
- },
- "id": {
- "type": "string"
- },
- "org": {
- "type": "string"
- },
- "role": {
- "type": "string"
- },
- "to": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "id",
- "role",
- "org",
- "from",
- "to",
- "description"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "headline": {
- "type": "string"
- },
- "indexable": {
- "type": "boolean"
- },
- "languages": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "level": {
- "type": "string"
- },
- "name": {
- "type": "string"
- }
- },
- "required": [
- "name",
- "level"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "links": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "label": {
- "type": "string"
- },
- "url": {
- "type": "string"
- }
- },
- "required": [
- "label",
- "url"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "model": {
- "items": {
- "additionalProperties": false,
- "properties": {
- "axis": {
- "type": "string"
- },
- "leans": {
- "type": "string"
- },
- "statement": {
- "type": "string"
- }
- },
- "required": [
- "axis",
- "leans",
- "statement"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "region": {
- "type": "string"
- },
- "showAvatar": {
- "type": "boolean"
- },
- "skills": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "tags": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "updatedAt": {
- "type": [
- "string",
- "null"
- ]
- },
- "visibility": {
- "enum": [
- "private",
- "members",
- "public"
- ],
- "type": "string"
- }
- },
- "required": [
- "headline",
- "about",
- "city",
- "region",
- "experience",
- "education",
- "skills",
- "languages",
- "links",
- "tags",
- "visibility",
- "indexable",
- "showAvatar",
- "model",
- "updatedAt"
- ],
- "type": "object"
- },
- "publicUrl": {
- "type": [
- "string",
- "null"
- ]
- },
- "reason": {
- "type": "string"
- },
- "waitingImport": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "none",
- "note"
- ],
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered structurally. The description adds only that the payload includes a visibility setting ('who sees it'), which hints at returned content but says nothing about format, size, or absent-field behavior. Modest value beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One compact sentence: subject and field inventory first, the sequencing rule last. Every clause earns its place with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only tool with no output schema, the definition supplies what an agent needs: what it returns (the section list) and when to call it relative to update_my_cv. Only the shape/size of the returned profile is left unspecified, which is a minor gap given no output schema exists.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so the baseline is 4. Nothing in the description conflicts with the empty schema, and there are no argument semantics to clarify.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Names the exact resource ('the person's own Profile & CV') and enumerates its constituent sections — headline, about, experience, education, skills, languages, links, visibility — making it clearly a retrieval of the caller's own profile. The 'own' qualifier implicitly separates it from read_profile/search_profiles, but the retrieval verb itself is only implied ('Read it before...') rather than stated up front.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'Read it before update_my_cv' gives an explicit ordering constraint and routes the agent toward the correct sibling. It doesn't explicitly say when to use read_profile or search_profiles instead, but the 'own' framing carries most of that distinction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.