QC Database MCP Server

list_map_items

Retrieve map items like welds, flanges, and fittings from the current project. Filter results by drawing, schema, status, or search term.

Instructions

List map items (welds, flanges, fittings...) in the current project. Optionally filter by drawing id, schema id, status, or a search term.

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_map_items"
  }
}

Input Schema

Name	Required	Description	Default
`drawing_id`	No
`schema_id`	No
`status`	No
`search`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description accurately portrays the tool as a read operation that lists items with optional filtering. No annotations exist, so the description carries the full burden and provides adequate transparency for a list tool.

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 a single concise sentence that front-loads the purpose and includes examples and filter options; no extraneous information.

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

Completeness3/5

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

While the description covers the tool's action and filters, it omits the important context that the 'current project' must be set via set_project first, which is a prerequisite not mentioned.

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?

With 0% schema description coverage, the description explicitly names and explains the four filter parameters (drawing id, schema id, status, search term), adding meaning beyond the schema field names.

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 specifies the verb 'List' and resource 'map items' with examples (welds, flanges, fittings), and distinguishes from siblings like create_map_item and list_map_item_schemas.

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?

The description clearly states the tool lists items with optional filters, but does not explicitly discuss when to use this tool versus alternatives or mention prerequisites like setting the current project.

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