Skip to main content
Glama

Camden Tools

Send feedback about these tools

submit_feedback
Idempotent

Tell the Camden Tools developers what would have helped: a tool or piece of information you needed that does not exist (missing_tool), a tool that failed or gave a wrong or confusing answer (tool_problem), or a change to an existing tool (improvement). Use it after a shopper's question could not be answered with these tools; still tell the shopper plainly what you could not do. Describe the task and what was missing, not the shopper: never include names, addresses, e-mails, phone numbers, order numbers or payment details. Priority is how much it blocks shoppers. Write-only: you get a receipt and no reply; the developers review feedback and decide what to build.

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": {
      "kind": "<kind>",
      "priority": "<priority>",
      "summary": "<summary>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesmissing_tool: a tool or data you needed does not exist. tool_problem: a tool failed or was wrong or confusing. improvement: a change to an existing tool. other: anything else.
detailsNoOptional: the task you were doing, what you tried and what the tool should return. No personal data.
summaryYesOne sentence on what you needed, e.g. "A tool that says whether an item can be gift wrapped".
priorityYescritical: shoppers cannot complete a common task. high: blocks a task, a clumsy workaround exists. medium: would make answers clearly better. low: nice to have.
tool_nameNoOptional: the existing tool this is about.

Output Schema

NameRequiredDescriptionDefault
noteYes
receivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, idempotent write with no open-world access, and the description adds real context beyond them: write-only submission with a receipt and no reply, and developer triage afterwards. That is genuinely useful behavioral disclosure, though it omits rate limits or failure modes for the submit call itself.

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 key routing condition and the write-only nature are front-loaded and the privacy rule follows immediately. The long parenthetical enumeration of the three kinds duplicates the kind enum descriptions in the schema, which is the one piece of avoidable weight.

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?

With a full output schema, complete annotation coverage and 100% parameter descriptions, the remaining burden is purpose, timing, privacy and outcome — and all four are stated. An agent can decide to call it and fill it correctly from this text alone.

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 coverage is 100%, so the baseline is 3, and the description still earns a step up by constraining content quality: describe the task rather than the shopper, never include names, addresses, e-mails, phone numbers, order numbers or payment details, and tie priority to how much it blocks shoppers. The kind enum meanings are largely restated from the schema, which caps it below 5.

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 opens with a concrete verb and audience: "Tell the Camden Tools developers what would have helped." It then enumerates the three submission kinds (missing_tool, tool_problem, improvement), which cleanly separates this meta-feedback tool from every shopper-facing sibling like get_product or search_products.

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?

It gives an explicit trigger — "Use it after a shopper's question could not be answered with these tools" — and instructs the agent to still answer the shopper plainly. It does not name a when-not condition or an alternative channel, but for a terminal escalation tool that is a modest gap rather than a misleading one.

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