Skip to main content
Glama

Absenderprofil prüfen

sender_profile_validate
Read-only

Prüft, ob ein Absenderprofil (per profileId) oder ein vorgeschlagener Feldsatz alle Pflichtangaben für seine Rechtsform enthält. Der Aufruf nimmt genau eine Form: profileId ODER rechtsform + proposedFields. proposedFields ist ein Objekt; ein JSON-kodierter Objekt-String wird ebenfalls akzeptiert. Liefert valid, missingFields und weiche Hinweise. Meldet eine Lücke als Ergebnis und läuft dabei durch. EN: Checks whether a sender profile (by profileId) or a proposed field set contains all mandatory details for its legal form. The call takes exactly one form: profileId OR rechtsform + proposedFields. proposedFields is an object; a JSON-encoded object string is also accepted. Returns valid, missingFields and soft hints. Reports a gap as a result and keeps running.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly/destructive=false/openWorld=false, so the bar is lower; the description still adds real value by naming the return payload (valid, missingFields, soft hints) and by stating that a gap is reported as a result rather than thrown ('Meldet eine Lücke als Ergebnis und läuft dabei durch'). It does not explain what a 'weicher Hinweis' looks like or what happens when profileId does not exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The input-shape rule and the return contract are front-loaded, which is good, but the entire description is duplicated verbatim in German and English, roughly doubling length without adding information. For a tool with a simple two-mode schema this is avoidable bulk.

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 no output schema, naming the three returned fields is necessary and it is done here; the mode exclusivity and the tested legal-form scoping are also covered. What remains unstated is whether validation has side effects or prerequisites (does the profileId have to exist first?) and how strict 'Pflichtangaben' is per Rechtsform.

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 honest baseline is 3, but the description adds information the schema cannot: proposedFields accepts a JSON-encoded object string even though the schema declares type object, which is a real behavioural widening an agent would otherwise miss. The oneOf exclusivity is restated rather than newly explained, and 'reasoning' is never mentioned.

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?

States a concrete verb+resource pair ('Prüft ... Absenderprofil') and immediately scopes the two possible input shapes, which cleanly separates it from sender_profile_get, sender_profile_list and sender_profile_upsert. An agent knows this is the read-only validation check, not a fetch or a write.

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?

Explicitly states the mode constraint: 'Der Aufruf nimmt genau eine Form: profileId ODER rechtsform + proposedFields', which is exactly the decision the calling agent has to make. It does not, however, say when to prefer this over sender_profile_get or that it should precede sender_profile_upsert, so no sibling exclusions are given.

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.