Skip to main content
Glama

Contact Novaeon

submit_inquiry

Send an inquiry to Novaeon on behalf of a person (same as the contact form; they reply by email). Only call this when the person asked to contact Novaeon and agreed to share their details. Ask them for any missing required field. Rate limited.

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": {
      "name": "<name>",
      "email": "<email>",
      "company": "<company>",
      "message": "<message>",
      "consent": "<consent>"
    },
    "name": "submit_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person
emailYesEmail address Novaeon should reply to
phoneNoPhone number (optional)
companyYesCompany and role of the person (required; write "private" or "freelancer" if that applies)
consentYesMust be true: the person agrees Novaeon stores these details to answer (https://novaeon.studio/privacy).
messageYesWhat they need: task or problem, systems involved, goal. At least 50 characters. Ask the person; never invent.
languageNoPreferred language code, e.g. en, ro, de (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / company / description
      Previous value: -"Company and/or role (optional)"New value: +"Company and role of the person (required; write \"private\" or \"freelancer\" if that applies)"
    • changedInput schema / properties / message / description
      Previous value: -"What they need (project, problem, questions). At least 10 characters."New value: +"What they need: task or problem, systems involved, goal. At least 50 characters. Ask the person; never invent."
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "email",
      -  "message",
      -  "consent"
      -]New value: +[
      +  "name",
      +  "email",
      +  "company",
      +  "message",
      +  "consent"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and readOnlyHint=false, so the external mutation is known; the description adds real context beyond that: the submission goes out as an email, the reply arrives by email, consent is mandatory, and the tool is 'Rate limited.' It does not describe failure behavior or what the tool returns on success, which keeps it below a 5.

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?

Three short sentences, each carrying a distinct payload: what it does, when it may be called, and how to handle missing fields, with the rate-limit caveat appended compactly. Nothing is repeated from the schema and nothing is padding.

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 7-parameter open-world write tool with no output schema, the definition covers trigger conditions, consent, sourcing of values, and rate limiting. The only gap is what the agent should report after a successful send, which is partly implied by 'they reply by email.'

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description genuinely adds value by telling the agent to source values from the person ('Ask them for any missing required field', 'never invent' for message). It says nothing about phone, language, or the URL embedded in consent, but the schema covers those.

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?

States a specific verb and resource ('Send an inquiry to Novaeon') plus the mechanism and outcome ('same as the contact form; they reply by email'). Combined with the 'on behalf of a person' framing, an agent can immediately tell this is a third-party contact-form submission and not a booking or lookup like the sibling 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?

Gives an explicit precondition: 'Only call this when the person asked to contact Novaeon and agreed to share their details.' That is a strong when-to-use gate, but no alternative is named for cases where the person merely wants information (e.g., get_studio_overview or find_service), so routing among siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources