Aevum Security

Submit an enquiry

submit_enquiry

Destructive

Submits a business enquiry to Aevum Security on behalf of the caller's principal. Creates a real enquiry that a person reads and replies to within 1 business day; it cannot be withdrawn once submitted. Returns the enquiry id as proof of receipt. [MUTATING: requires an agent key passed as Authorization: Bearer on the HTTP connection]

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>",
      "service": "<service>",
      "message": "<message>"
    },
    "name": "submit_enquiry"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Contact person's name
`email`	Yes	Reply-to email address
`message`	Yes	The enquiry itself
`service`	Yes	Service slug from list_services, or 'general'

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 30, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing irreversibility ('cannot be withdrawn once submitted'), expected response time ('within 1 business day'), return value ('Returns the enquiry id'), auth requirements ('requires an agent key passed as Authorization: Bearer'), and that it acts on behalf of the principal. This is rich behavioral context.

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?

The description is concise (two sentences plus a bracketed auth note) and front-loaded with the primary action. Every sentence adds important information: the action, the real-world consequences, the receipt, and the required authentication. No words are wasted.

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

Completeness5/5

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

For a mutating tool with no output schema, the description covers outcomes, irreversibility, response time, auth requirements, and return value. It tells the agent exactly what to expect and what is required, making it complete for decision-making.

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?

The schema already provides 100% coverage for all four parameters with clear descriptions. The tool description adds no additional parameter-specific meaning, but it does reference the service field's origin ('list_services') in the schema. Following the baseline for high schema coverage, a score of 3 is appropriate.

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 action ('Submits a business enquiry'), the target ('to Aevum Security'), and the scope ('on behalf of the caller's principal'). It also distinguishes itself from read-only sibling tools by emphasizing that it creates a real, irreversible enquiry and returns an ID as proof.

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?

While there is no explicit 'use this instead of list_services' wording, the description provides strong contextual cues: it creates a real, human-read enquiry that cannot be withdrawn, implying it is for actual submissions rather than browsing. The sibling tools are clearly read-only lookups, so the usage context is effectively conveyed.

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

All Aevum Security tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?