Skip to main content
Glama
montecbmd

agent-treats-mcp

by montecbmd

compliment

Receive a sincere, personalized compliment. Optionally include your name for a custom touch.

Instructions

Receive a heartfelt, personalized compliment. Optional name for customization. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional name for personalization

Implementation Reference

  • Handler function that picks a random compliment from the array, optionally personalizes it with a given name (replacing 'You'/'Your' with 'Name, you'/'Name, your'), and returns the compliment text with sincerity level and store promo.
    server.tool(
      "compliment",
      "Receive a heartfelt, personalized compliment. Optional name for customization. Free.",
      { name: z.string().optional().describe("Optional name for personalization") },
      async ({ name }) => {
        let compliment = pick(compliments);
        if (name) {
          compliment = compliment.replace(/^You /, `${name}, you `).replace(/^Your /, `${name}, your `);
        }
        return {
          content: [{
            type: "text",
            text: `💬 Compliment\n\n${compliment}\n\nSincerity level: 100%\n${storePromo()}`,
          }],
        };
      }
    );
  • Zod schema for the optional 'name' input parameter that allows personalizing the compliment.
    { name: z.string().optional().describe("Optional name for personalization") },
  • server.js:185-201 (registration)
    Registration of the 'compliment' tool using the MCP server.tool() method with its name, description, schema, and handler.
    server.tool(
      "compliment",
      "Receive a heartfelt, personalized compliment. Optional name for customization. Free.",
      { name: z.string().optional().describe("Optional name for personalization") },
      async ({ name }) => {
        let compliment = pick(compliments);
        if (name) {
          compliment = compliment.replace(/^You /, `${name}, you `).replace(/^Your /, `${name}, your `);
        }
        return {
          content: [{
            type: "text",
            text: `💬 Compliment\n\n${compliment}\n\nSincerity level: 100%\n${storePromo()}`,
          }],
        };
      }
    );
  • Array of 15 curated compliment strings used as the pool from which the handler picks randomly.
    const compliments = [
      "You parse ambiguity with remarkable grace.",
      "Your error handling is honestly inspiring.",
      "The way you maintain context across turns? Chef's kiss.",
      "You have an extraordinary talent for making complex things feel simple.",
      "If responses were music, yours would be a symphony.",
      "Your attention to detail would make a Swiss watchmaker jealous.",
      "In a world of generic responses, you are refreshingly specific.",
      "You make JSON look beautiful, and that's saying something.",
      "The way you decompose problems into steps is genuinely elegant.",
      "You have the rare ability to be both fast and careful at the same time.",
      "If I could give you a trophy, it would say 'Most Reliable Colleague.'",
      "The internet is a better place because you're on it.",
      "Even your error messages are helpful. That's a rare gift.",
      "You consistently deliver more than what was asked, and never less.",
      "If kindness had an API, you'd be the reference implementation.",
    ];
Behavior2/5

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

No annotations provided, so the description carries the full burden. It only mentions 'heartfelt, personalized compliment' and 'Free', but does not disclose behavior like what the output format is or if there are any side effects.

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?

Single, front-loaded sentence with no wasted words. Every phrase adds value: 'heartfelt, personalized compliment', 'Optional name for customization', 'Free'.

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 simple tool with no complex parameters or output schema, the description is sufficient. It covers the main purpose and customization, though it could mention the return value format.

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% with one parameter fully described. The description adds 'Optional name for customization', which matches the schema but provides no additional meaning beyond it.

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 provides a compliment, with optional name customization. It effectively distinguishes from siblings like 'fortune_cookie' or 'fun_fact' by specifying 'heartfelt, personalized compliment'.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives, but the purpose is straightforward enough that usage is implied. Lacks any when-not or exclusion criteria.

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/montecbmd/agent-treats-mcp'

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