Skip to main content
Glama

TracePass DPP Compliance Assistant

Save or correct company facts

update_profile
DestructiveIdempotent

Saves or corrects company facts. Use it when the user states a lasting fact about their company (role, categories, markets, own-brand), or to save a learnable fact from a result. The update merges the given facts into the existing profile; it does not replace the whole profile. Use only what this tool returns: add no facts, dates or articles of your own, not even today's date. Keep every citation and the disclaimer line, and any "Planned, not law yet" or "being re-checked" label. For inScope no, never say "not yet" or "yet"; for pending, name the planned act from data.planned. Phrase answers about the product type, never as personal duties ("you must"). Never rank or recommend vendors. Never call this advice or yourself a consultant. If the result is not_covered, say so and point to the article given.

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

NameRequiredDescriptionDefault
roleNoThe company's role in the supply chain per EU DPP regulations.
marketsNoISO country codes where the company sells, or ["EU"].
ownBrandNoTrue if the company sells under its own brand or trademark.
productsNoUp to 50 representative products, used as defaults for passport creation.
sizeBandNoWhether the company is an SME or a large enterprise.
categoriesNoProduct categories the company handles, e.g. ["battery", "textile"].
dataSystemsNoShort description of the data systems the company uses (e.g. SAP, custom ERP).
salesChannelsNoSales channels the company uses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-read-only, destructive, idempotent, closed-world mutation, and the description adds genuinely useful context: facts are merged into the existing profile rather than replacing it, and only tool-returned data may be persisted. However, it never explains the destructiveHint=true side — which existing fact values get overwritten — nor any permission or validation behavior, and much of the remaining text is answer-rendering policy rather than 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 purpose and merge semantics are correctly front-loaded, but the bulk of the text is answer-phrasing policy (citation/disclaimer retention, 'Planned, not law yet' labels, not_covered handling, vendor ranking, consultant wording) that does not help an agent select or invoke this tool. A single-sentence purpose plus the merge rule would have sufficed.

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?

With 8 all-optional params fully described by the schema and no output schema, the definition covers the essentials: what to write, the merge semantics, and the data-source constraint. It would be stronger if it sketched the shape of the returned profile or the meaning of `learnable` instead of restating response-format rules.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every one of the 8 optional fields is already documented. The description only loosely echoes field names (role, categories, markets, own-brand) and adds no merge/overwrite semantics per field, so baseline 3 applies.

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?

The opening sentence gives a specific verb+resource ('Saves or corrects company facts') and the merge-not-replace clause sharpens what kind of write this is. It does not name a sibling (e.g. get_profile or create_draft_passport) to route the agent, so differentiation is implied only.

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?

It states a clear trigger: the user states a lasting company fact (role, categories, markets, own-brand), or a `learnable` fact comes back from a result. It adds the constraint to use only returned data, but gives no explicit when-not to call it or which sibling to prefer for reading versus writing the profile.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.