Skip to main content
Glama

triage_contact_enquiry

Idempotent

Reopen, mark read or close a specific enquiry for a contact in the approved business.

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": {
      "contactId": "<contactId>",
      "enquiryId": "<enquiryId>",
      "action": "<action>"
    },
    "name": "triage_contact_enquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
contactIdYes
enquiryIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the mutation and safety profile is covered. The description adds useful scope (operations are confined to a contact's enquiry within the approved business) but says nothing about side effects such as notifications, whether close is reversible, or failure modes.

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 front-loaded sentence with the action set leading and the resource scope following; no filler. It is efficient but arguably under-specified rather than over-long.

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?

For a three-parameter mutation with no output schema and zero schema description coverage, the description leaves too much open: the identity/format of the two IDs, whether contactId and enquiryId must be consistent, and what the caller gets back on success or partial failure are all unaddressed.

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 coverage is 0%, so the description must carry parameter meaning and largely doesn't. It enumerates the action values that already appear in the enum, but says nothing about what contactId and enquiryId are, their accepted format, or how to obtain them.

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 set (reopen, mark read, close) applied to a concrete resource (an enquiry belonging to a contact), scoped to "the approved business." An agent can tell this is a per-enquiry state-changing operation, though nothing distinguishes it from nearby tools such as update_pipeline_enquiry.

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 pick this tool over alternatives like update_pipeline_enquiry or mark_contact_messages_read, nor any stated prerequisites (e.g., whether the enquiry must already exist or what state transitions are legal). The three actions are listed, but the choice between them is left entirely to the caller.

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