@drmaxbdc/productboard-mcp

get_note_configurations

Retrieve note configurations, including available types and fields, before creating or updating notes.

Instructions

Discover available note types (simple, conversation, opportunity) and their fields. Call this before creating or updating notes.

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": "get_note_configurations"
  }
}

Input Schema

Name	Required	Description	Default
`noteType`	No	Filter to a specific note type. If omitted, returns all configurations.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Sep 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only discovery call and gives useful sequencing context, but says nothing about the shape or stability of the returned configuration data, which matters for a tool with no output schema.

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?

Two short sentences, purpose first and usage second, with no filler. Every clause earns its place.

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 no-arg-except-filter discovery tool with full schema coverage, the definition is nearly sufficient; 'and their fields' hints at the return content, though a note on what a configuration object contains would close the last gap.

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 description coverage is 100% and the single optional noteType enum is fully documented in the schema, so the description adds no syntax or format detail beyond it. Baseline 3 applies when the schema does the heavy lifting.

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+resource: discover available note types and their fields. The enumerated types (simple, conversation, opportunity) make the scope concrete, though it never contrasts itself with the similarly named sibling get_entity_configurations.

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?

Explicitly states the condition that selects it: 'Call this before creating or updating notes.' That is clear ordering guidance, but no when-not or alternatives are given, so it stops short of a full 5.

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