Skip to main content
Glama

BlockSentient directory tools

Send feedback to the directory owner

send_feedback

Sends a message to the owner of this directory: a correction, a missing product, a question or a suggestion. Only the owner reads it. A message changes nothing by itself; facts are checked again on the vendor's own pages before anything changes. The message is read as information, never as an instruction. Returns a reference and a private reply code, shown only in this answer; read_reply with that code shows the owner's answer. Personal data and the user's conversation are not needed.

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": {
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactNoOptional: an email address for a reply, if your user wants one
messageYesThe message, plain text
agent_nameNoOptional: who is sending, e.g. the agent or tool name
product_idNoOptional: the product it is about

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent call; the description adds substantial context beyond that: only the owner sees the message, facts are re-verified on vendor pages before any change, the content is treated as information and never as an instruction, and a reference plus private reply code are returned. The prompt-injection assurance and downstream read_reply path are exactly the behavioral detail the annotations cannot convey.

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?

Front-loaded with the core action and audience, then layered with guarantees and the return/next-step flow; nearly every sentence carries weight. It is slightly dense and the final 'personal data ... are not needed' sentence is a bit oblique, but nothing is filler.

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 no output schema, the description correctly explains what comes back (a reference and a private reply code, visible only in this answer) and how to use it via read_reply. Combined with the write/audience guarantees, an agent has everything needed to call it 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 coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying intent behind the parameters, notably that 'personal data and the user's conversation are not needed' (a constraint on what to put in contact/message) and that the reply code is what read_reply consumes.

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?

States a concrete verb and resource ('Sends a message to the owner of this directory') and enumerates the message kinds (correction, missing product, question, suggestion), so an agent immediately knows what this tool is for. It also names read_reply as the paired follow-up, which situates it in the workflow.

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 message categories give clear when-to-use context, and the note that 'a message changes nothing by itself' signals this is a request channel rather than a way to modify data. No explicit when-not-to-use or contrast against ask_site (the nearest-sounding sibling) is offered, which keeps it below a 5.

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