Skip to main content
Glama

list_inquiries

Read-only

Lists all vendor inquiries with vendor name, status, and unread flag, helping you track and review wedding vendor communication.

Instructions

List all vendor inquiries with status, vendor name, and unread flag

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_inquiries"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"full" (default) returns the usual JSON; "brief" returns one line per item: title — <ISO date or "no date"> — <status>. The date is the last update; status is read/unread (and booked).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.1
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns the usual JSON; \"brief\" returns one line per item: title — <ISO date or \"no date\"> — <status>. The date is the last update; status is read/unread (and booked).",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.4.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful return-field context (status, vendor name, unread flag), which matters because there is no output schema, but says nothing about pagination, ordering, or filtering behavior.

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?

A single front-loaded sentence with zero filler; the resource and returned fields are stated up front and nothing is repeated.

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 zero-required-parameter list tool with no output schema, describing the returned fields is the key contribution and it is delivered. Missing is routing guidance versus sibling inquiry tools and note of pagination/ordering, which are minor but real gaps.

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 the single 'view' parameter has a thorough enum description covering both 'full' and 'brief' output shapes. The tool description never mentions this parameter, so it adds no meaning beyond the schema — baseline 3 applies.

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?

States a specific verb and resource ('List all vendor inquiries') plus the fields returned, so the agent knows exactly what this fetches. It does not name or distinguish itself from siblings like get_inquiry_conversation or mark_inquiry_read, which keeps it below a 5.

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 when-to-use guidance at all: no mention of when to prefer this over get_inquiry_conversation for a single thread, or mark_inquiry_read when unread flags are the concern. The word 'all' implies a bulk listing scope, but that is the only hint.

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