Skip to main content
Glama
Sign In
Fider MCP Server

Fider MCP Server

by ringostat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

respond_to_post

Change the status of a customer feedback post to open, planned, started, completed, declined, or duplicate, optionally adding a comment. Requires collaborator or admin role.

Instructions

Respond to a post by changing its status (requires collaborator/admin role)

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": {
      "number": "<number>",
      "status": "<status>"
    },
    "name": "respond_to_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoOptional description of the status change
numberYesThe post number to respond to
statusYesThe new status of the post
originalNumberNoRequired when status is 'duplicate' - the post number to merge into

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It adds a role requirement beyond the schema, which is helpful, but does not disclose side effects such as notifications, reversibility, or what happens when the 'duplicate' status is set.

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?

The description is a single concise sentence that states the core action and a key constraint (role requirement). No filler or redundancy.

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 mutation tool with four parameters and no output schema, the description provides enough to understand the core behavior. Combined with the schema, it covers the conditional 'duplicate' requirement, though it could add a bit more context about the workflow or consequences.

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 descriptions cover all four parameters, so the description does not need to compensate. It adds no additional parameter semantics beyond what the schema already documents.

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 clearly identifies the action (responding by changing status) and resource (a post). 'Changing its status' distinguishes it from edit_post and add_comment, making the tool's purpose unambiguous.

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 mentions a required role (collaborator/admin), which is a useful constraint, but it does not explicitly state when to use this tool versus alternatives like edit_post or add_comment. Usage is implied rather than prescribed.

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