push_contempt_mcp

Overview Schema Source Related Servers Discussions Admin

saluta

Produces a greeting for a named person, with optional formal tone, to personalize assistant responses when addressing someone.

Instructions

Restituisce un saluto per la persona indicata.

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": {
      "nome": "<nome>"
    },
    "name": "saluta"
  }
}

Input Schema

Name	Required	Description	Default
`nome`	Yes
`formale`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not say whether the operation is side-effect free, how the 'formale' flag changes output, or what the returned greeting looks like. For a zero-annotation tool this is a meaningful gap, even for a simple operation.

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?

A single efficient sentence with no wasted words and no awkward framing. It is appropriately sized for a trivial tool, though it could have spent a few more words on the 'formale' parameter instead of nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return format needn't be explained, but with 0% schema coverage the description still leaves 'formale' entirely undefined. For a two-parameter tool, omitting the semantic effect of half the inputs is incomplete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for two undocumented parameters. It only loosely implies 'nome' via 'persona indicata' and says nothing about 'formale', which materially changes the output format (formal vs informal greeting).

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 states a specific verb and resource: it returns a greeting for the indicated person. The purpose is unambiguous and trivially distinguishable from the catalog/SEO/order siblings. It does not, however, describe how the name is incorporated or what kind of greeting is produced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. Being a trivial greeting tool lowers the stakes, but the description still offers no usage context at all.

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