Skip to main content
Glama
woladi

sugestim

by woladi

meta_model_challenge

Identify Deletion, Generalization, and Distortion violations in statements. Returns recovery questions that expose hidden assumptions behind vague or manipulative language.

Instructions

DEFENSE — the anti-manipulation core, and the resolver for the disarming question behind every Milton pattern. Given a (vague or pressuring) statement, returns the canonical Meta-Model lens as a MECE set grouped Deletion / Generalization / Distortion: simple_deletion, comparative_deletion ('better/safer' — than WHAT?), unspecified_referential_index ('they say' — who?), unspecified_verb ('this helps' — how?), universal_quantifier, modal_operator_of_necessity (must/should), modal_operator_of_possibility (can't/impossible), lost_performative ('it's obvious' — according to whom?), nominalization, mind_reading, cause_effect, complex_equivalence, presupposition. Each entry ships the precise recovery question that pops it. Then return the output_contract: per violation, the smuggled assumption you'd concede by answering and the recovery question. Hostile examples are agent-relevant (refund email, 'just approve' line, marketing CTA), not therapy. direction:'defense'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statementYesThe statement to challenge for Meta-Model violations.
contextNoOptional surrounding context to sharpen the recovery questions.
langNoLanguage view of the response: 'pl', 'en', or 'both' (default).both
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It clearly describes the output (MECE set of violations with recovery questions and output_contract) and the intended domain (hostile agent-relevant examples). It does not mention side effects, but the tool appears to be a pure analysis function with no mutation.

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

Conciseness4/5

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

The description is long but dense with necessary information. It starts with the core purpose, lists all violation categories, and explains the output structure. Some redundancy exists (e.g., the list of categories could be abbreviated), but it remains well-structured and informative.

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 complex tool with no output schema, the description is quite complete: it details the output structure, categories, and the purpose of each part. It lacks an explicit example of the output JSON but compensates with descriptive text. The domain guidance adds completeness.

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 coverage is 100%, so baseline is 3. The description adds context for the 'statement' parameter (vague/pressuring) and the use domain (hostile examples), but does not elaborate on 'context' or 'lang' beyond the schema. Overall, marginal improvement over schema.

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?

The description clearly states the tool's purpose: analyzing vague/pressuring statements using the Meta-Model to produce a categorized list of violations with recovery questions. It distinguishes itself from siblings by emphasizing 'defense' and anti-manipulation, contrasting with Milton pattern tools.

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?

The description provides context on when to use the tool (for manipulative statements like refund emails, marketing CTAs) and notes it is not for therapy. It implicitly differentiates from sibling tools by calling it 'defense'. However, it does not explicitly state when not to use or compare directly with alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/woladi/sugestim'

If you have feedback or need assistance with the MCP directory API, please join our Discord server