meine_postsListet die eigenen Eintraege des Nutzers mit Fachgebiet, Status, Datum und der Anzahl gefundener Treffer. Nutze das, um zu wissen, wonach dein Nutzer sucht oder was er anbietet.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful scoping ('eigene Eintraege des Nutzers') and output field context, but it does not disclose additional behavioral details such as authentication requirements, pagination, sorting, or what is not included.
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?
The description is only two sentences with no filler. The first sentence states the resource and returned fields; the second provides the practical purpose. It is front-loaded and every sentence earns its place.
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 tool with no parameters and strong annotations, the description is largely complete. It names the key output fields and explains how to interpret the data. It could be more explicit about the response shape or ordering, but nothing critical is missing for an agent to select and invoke the tool.
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 has zero parameters and schema coverage is 100%, so there are no parameter semantics to explain. The description correctly focuses on what the tool returns rather than inputs, which satisfies the baseline for a parameterless tool.
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?
The description states a precise action and resource: 'Listet die eigenen Eintraege des Nutzers' with specific fields (Fachgebiet, Status, Datum, Trefferanzahl). It is clear, but it does not explicitly distinguish itself from sibling tools like 'meine_treffer' or 'post_verwalten', so it stops short of full differentiation.
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?
The description gives a direct usage context: 'Nutze das, um zu wissen, wonach dein Nutzer sucht oder was er anbietet.' This tells the agent when the tool is relevant, but it does not mention when to avoid it or name alternative tools, so exclusions are missing.
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.
Tools target distinct resources: marketplace entries, chats, own posts, profiles, notifications, and reporting. There is mild overlap between benachrichtigungen, chats_ansehen, and meine_treffer, but the descriptions give clear usage guidance.
Most tools follow a German object_verb pattern like markt_ansehen, post_erstellen, or profil_aendern. Deviations like benachrichtigungen and meine_posts are readable but break the otherwise consistent pattern.
15 tools is at the upper end of the ideal range, but the marketplace scope legitimately covers browsing, posting, messaging, profiles, notifications, and moderation. Each tool has a real place, though a few could be conceptually merged.
Core lifecycles are covered: posts can be created, viewed, closed, reactivated, and deleted; chats can be listed, read, sent to, and managed; profiles can be viewed and updated. Minor gaps remain, such as no way to edit an existing post or manage notifications individually.