Skip to main content
Glama

North Carolina DMV

by io.github.pipeworx-io
OverviewAdmin

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / claim_token
      Added value: +{
+  "description": "Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "type",
-  "message"
-]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare non-readonly, non-idempotent behavior, but the description goes far beyond: it discloses rate limiting (5 per identifier per day), that filing without an account returns a claim_token for later lookup, that reports are read daily, and that feedback affects roadmap. It also clarifies it's free and doesn't count against quota. This richly compensates for the sparse annotations.

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?

The description is dense but well-structured: it front-loads the purpose, then gives usage guidance, exclusions, the claim_token workflow, and operational notes. Every sentence adds valuable information, though the length is substantial. It earns a 4 rather than 5 because it could arguably be tightened without losing key guidance.

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?

Given the tool's complexity (4 optional params, nested context object, follow-up workflow, rate limits) and no output schema, the description is remarkably complete. It explains the follow-up mechanism (claim_token), appropriate message content, what to avoid (pasting end-user prompts, reporting other servers' issues), and operational characteristics. There's no obvious missing information an agent would need to use this tool correctly.

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?

Schema description coverage is 100%, with each parameter already documented in the schema. The description adds value by explaining the claim_token workflow (pass token back with no other arguments to read status), the message length guidance (1-2 sentences typical, 2000 chars), and the semantic categories (bug vs feature vs data_gap vs praise). This exceeds the baseline 3 for full schema coverage, though it doesn't detail the context object's nested fields beyond what schema says.

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 tool sends feedback to the Pipeworx team about broken, missing, or praise-worthy functionality. It specifies the resource (Pipeworx team) and the verb (tell/report), and distinguishes itself from sibling research/subscription tools by focusing on reporting issues about the Pipeworx toolset itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: use for bug reports, feature requests, data gaps, praise, and NOT for other MCP servers' tools. It even includes a decision rule for uncertainty ('Pipeworx tool names are the ones this connection lists') and describes the daily use case for claim_token follow-up. This is exceptional guidance.

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

All North Carolina DMV toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources