Skip to main content
Glama
Sign In
apinoa-mcp

apinoa-mcp

Official
by apinoahq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read a feedback report's status

get_feedback
Read-only

Retrieves the status of a report sent with send_feedback (received, in_progress, resolved or declined) plus our reply, by its id. Use it to check feedback progress.

Instructions

The status of a report sent with send_feedback (received, in_progress, resolved or declined) and our reply, by its id. Free.

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": {
      "id": "<id>"
    },
    "name": "get_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id send_feedback returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.18

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds useful detail beyond that by enumerating the exact status values and noting the reply is returned. The single word 'Free' discloses a non-obvious cost trait not captured in annotations. It does not mention error behavior for invalid ids or how long statuses take to update.

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?

One compact sentence front-loads the resource and status values, with the id requirement following. The trailing 'Free' is terse but earns its place as a cost disclosure; there is no filler or repetition.

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

Completeness4/5

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

For a one-parameter read tool with full schema coverage and annotations covering safety and openness, this is nearly complete: it names the source of the id, the returnable states, and the reply. Only absence of output-schema detail and error semantics leaves a small gap.

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 100% and the schema already documents that the single parameter is the id returned by send_feedback. The description reinforces that linkage and adds nothing further about format constraints, so baseline 3 is appropriate.

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 specific verb and resource ('The status of a report'), names the originating sibling (send_feedback), and enumerates the possible values (received, in_progress, resolved, declined). An agent can distinguish this read-back tool from send_feedback without opening either schema.

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

Usage Guidelines3/5

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

The description ties the tool to send_feedback, implying it is used after submitting a report, and specifies the id is the one send_feedback returned. However, it never explicitly says when not to use it or what to do if the id is unknown, so guidance is implied rather than stated.

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

Deploy Server

Other Tools