Skip to main content
Glama
Hermoso

Hermoso

Official

Contact Hermoso support

contact_support

Message Hermoso's human support team for billing, sign-in, or connector problems the tools cannot resolve; the team replies by email to the account address.

Instructions

Message Hermoso's human support team for the user: billing, account or sign-in problems, a connector that will not connect, or a question the tools cannot answer. Use the user's words. The team replies by email to the account's address (the result names it). Defects you found: report_bug. Missing capabilities: request_feature. Free.

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": {
      "message": "<message>"
    },
    "name": "contact_support"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNowhere it happened: a tool, page or job id
messageYesthe user's question, in their words, with what they tried

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.610

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the mutation and external-reach profile is already covered. The description adds genuinely new facts: the team replies by email to the account's address, the result names that address, and the call is free (no credit cost). It does not say whether the message is sent immediately or what the response looks like, but the result-naming note covers the practical gap.

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?

Front-loaded with the purpose and the triggering scenarios, then the sibling routing, then the reply channel. The telegraphic fragment style ('Free.') is efficient rather than unclear, though it borders on terseness in places.

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 two-parameter, no-output-schema tool, this covers what an agent needs: when to call it, how to phrase the message, where the reply goes, and which sibling to prefer for adjacent needs. The only omission is any statement about confirmation or immediacy of sending.

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% and both parameters are documented, so the baseline is 3. The instruction 'Use the user's words' reinforces the message field but largely restates what the schema description already says; nothing is added about the 'page' parameter's expected format.

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?

Names a specific verb and resource ('Message Hermoso's human support team') and immediately scopes what belongs there: billing, account or sign-in problems, broken connectors, or questions the tools cannot answer. It explicitly distinguishes itself from two siblings by routing defects to report_bug and missing capabilities to request_feature.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use list and explicit when-not-to-use routing ('Defects you found: report_bug. Missing capabilities: request_feature.'). The boundary between contacting support and filing a bug or feature request is unambiguous.

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

Deploy Server

Other Tools