Skip to main content
Glama

record_feedback

Collect feedback on prompt enhancement techniques to improve future responses by tracking helpfulness of applied methods.

Instructions

Record whether an enhancement was helpful.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
techniqueYesTechnique ID
helpfulYesWas it helpful?
promptNoThe original prompt (for context)

Implementation Reference

  • The handler for the 'record_feedback' tool, which uses `recordDecision` to store the feedback.
    case 'record_feedback': {
      const { technique, helpful, prompt = '' } = args;
      recordDecision({ prompt, technique, accepted: true, helpful });
      return { recorded: true };
    }
  • The schema definition for the 'record_feedback' tool in the tool list response.
      name: 'record_feedback',
      description: 'Record whether an enhancement was helpful.',
      inputSchema: {
        type: 'object',
        properties: {
          technique: { type: 'string', description: 'Technique ID' },
          helpful: { type: 'boolean', description: 'Was it helpful?' },
          prompt: { type: 'string', description: 'The original prompt (for context)' },
        },
        required: ['technique', 'helpful'],
      },
    },
Behavior2/5

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

No annotations provided, so description carries full burden. 'Record' implies write persistence but lacks disclosure of side effects, idempotency, overwrite behavior, or what happens to recorded data.

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?

Single sentence, front-loaded, no redundancy. Efficient but arguably too terse given missing workflow and behavioral context.

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

Completeness2/5

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

Omits critical context for a feedback tool: relationship to enhance_prompt workflow, whether feedback is anonymous/required, and data persistence. With siblings providing the 'enhancement' being rated, should explicitly state this closes the feedback loop.

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 has 100% description coverage, establishing baseline 3. Description adds semantic context ('enhancement was helpful') mapping to 'technique' and 'helpful' params but doesn't elaborate syntax or optional 'prompt' usage beyond schema.

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?

Clear verb ('Record') and resource ('feedback'/'whether helpful'). Mentions 'enhancement' which links to the 'enhance_prompt' sibling, distinguishing this as the feedback mechanism versus the enhancement generator.

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?

No explicit guidance on when to use (e.g., 'call after enhance_prompt') or when not to use. Lacks workflow integration instructions despite clear relationship to sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlanRoybal/prompte-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server