Skip to main content
Glama

Samuelz® Policy

Unternehmensprofil speichern

confirm_company_profile
Destructive

App-only exact human Owner confirmation. Never call from the model or infer approval from chat text.

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": {
      "candidate": "<candidate>",
      "approvalToken": "<approvalToken>"
    },
    "name": "confirm_company_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidateYesExact candidate from the matching card's hidden metadata, including the change and expiry. The trusted UI copies every field unchanged; never reconstruct it from chat.
approvalTokenYesOpaque approval proof supplied in hidden metadata by the matching show tool. The trusted UI copies it unchanged; never construct it or request it from chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructive=true, readOnly=false, idempotent=false, so the mutation risk is covered; the description adds genuinely new context — that a human Owner must confirm in the app and that chat text can never constitute approval. It stops short of describing what happens on success, on a revision mismatch, or on token expiry, though the schema carries the expiry/revision semantics.

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?

Two short sentences, zero filler, and the hardest constraint (app-only, never from the model) is front-loaded where the agent will read it first. Nothing is redundant with the title or schema.

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 destructive, human-gated write with a complex nested schema and no output schema, the definition covers the critical thing an agent needs — that it must not self-invoke. A sentence on the post-confirmation outcome and the named upstream show/prepare tool would close the remaining gap.

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%, and the nested candidate/approvalToken fields already document that values must be copied unchanged from trusted UI metadata. The description's 'exact' and 'never infer approval from chat text' reinforce that contract but add no new per-parameter meaning, so the baseline of 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 description names the action (an exact human Owner confirmation) and the resource indirectly through the tool name and title ('company profile' / 'Unternehmensprofil speichern'), making it clear this is the commit gate for a company profile change. It does not, however, explicitly say it applies a previously prepared preview, so the link to prepare_company_profile_change / show_company_profile_approval must be inferred.

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?

'Never call from the model' and 'App-only' give an unambiguous exclusion that an agent can act on immediately, which is rarer and more valuable than generic when-to-use prose. The positive case (the trusted UI invokes it after a human approves) is only implied, and no sibling tool is named as the source of the approval token, leaving a small gap.

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.

Resources