Djinni MCP

Overview Schema Source Related Servers Discussions Admin

update_profile

Save explicit profile changes and apply questionnaire overrides to CV facts; set null to remove an override, or replace CV facts only after a user-requested import or refresh.

Instructions

Save explicit user changes. Questionnaire patches override CV facts; null removes an override. Supplied resume_facts REPLACES the CV section: use only after a user-requested import/refresh. Never automatically reread documents.

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

Input Schema

Name	Required	Description	Default
`resume_facts`	No
`questionnaire`	No

Output Schema

Name	Required	Description	Default
`fields`	No
`version`	No
`updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 9, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the two different merge semantics: questionnaire keys patch and "null removes an override," while resume_facts "REPLACES the CV section" wholesale. That overwrite warning is exactly the kind of consequence an agent cannot infer from destructiveHint=false alone, and it is surfaced prominently.

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 short sentences, front-loaded with the core action, then the per-parameter semantics, then the guardrail. Every clause carries operational meaning and nothing is repeated from the schema or annotations.

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?

For a zero-required-parameter mutation tool with an output schema already covering return values, the description supplies the essential safety context: merge vs. replace behavior, null-override removal, and the user-initiated-only rule. Only the absence of an explicit sibling reference keeps it from being fully complete.

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 description coverage is 0%, so the description carries the full burden, and it does explain the semantics of both parameters: questionnaire behaves as a patch with null-as-delete, resume_facts as a full replacement. It does not mention the key-format or size constraints encoded in the schema, but those are enforced structurally.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Save explicit user changes" states a specific verb plus the resource (profile changes), and the following sentences clarify the two distinct data channels (questionnaire patches vs. resume_facts replacement). It never names a sibling tool, so the read/write distinction with get_profile must be inferred from "never automatically reread documents."

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?

Provides an explicit precondition for the risky path: resume_facts should be used "only after a user-requested import/refresh," plus a clear exclusion, "Never automatically reread documents." It stops short of naming get_profile as the alternative read path, so the routing is implied rather than stated.

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

Deploy Server