Skip to main content
Glama

Borders

Send feedback

send_feedback

Use this when the person asks to tell Borders something: a wrong wait, a missing crossing, an idea. Only their words, never include the conversation. Not for questions about a wait: answer from the other tools.

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

Input Schema

NameRequiredDescriptionDefault
kindYesproblem, idea or question
textYes
toolNo

Output Schema

NameRequiredDescriptionDefault
sentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, so safety is covered. The description adds a real content constraint beyond that: submit only the person's own words and never include the conversation transcript. It does not say what happens after submission or whether the user sees a confirmation, but the return shape is covered by the 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?

Three compact sentences, front-loaded with the trigger, then the content rule, then the exclusion. No filler and no repetition of the schema.

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

Completeness3/5

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

Output schema and annotations remove the need to explain return values or safety, and the core usage rule is present. However, the 'tool' parameter is opaque and the enum offers 'question' while the description steers wait questions elsewhere, a distinction worth one clarifying clause for an agent filling this in.

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 coverage is only 33%: 'kind' has an enum description that merely restates its values, while 'text' and 'tool' have none. The description helps by clarifying that 'text' must be the person's verbatim words and by giving content examples that map onto problem/idea, but the 'tool' parameter (maxLength 100) is left entirely unexplained in both schema and description.

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 states a specific verb and target — the person telling Borders about a wrong wait, a missing crossing, or an idea — so an agent can immediately tell this is a feedback-submission tool rather than a lookup. It also explicitly separates itself from the border-data siblings by saying wait questions belong to other tools.

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?

It gives both the trigger ('when the person asks to tell Borders something') and an explicit exclusion ('Not for questions about a wait: answer from the other tools'). The routing decision is fully specified rather than implied.

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