fenbs

fenbs_flag_item

Idempotent

Flag a task, or take a flag off. which "mine" is the flag only the person you act for sees (any board; needs only to see it). which "business" is the flag everybody on a team board sees; it needs the "Flag for everyone" permission and is refused on a personal board. Use a flag for "look at this"; the note, plan and comments still say why.

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": {
      "ref": "<ref>",
      "which": "<which>"
    },
    "name": "fenbs_flag_item"
  }
}

Input Schema

Name	Required	Description
`on`	No	true to flag, false to take the flag off. Default true.
`ref`	Yes
`which`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the description adds genuine value: the permission requirement for 'business' flags and the failure mode on personal boards. It also documents 'on=false' as the unflag path, which the agent needs to know this tool is bidirectional rather than purely additive.

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?

Compact and front-loaded: the action comes first, then mode semantics, then intent. Phrasing is slightly convoluted (nested quotes around 'mine'/'business' and reversed word order in 'which "mine" is the flag'), but nothing is padded.

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 three-parameter mutation with no output schema, the description covers permission requirements, the error condition on personal boards, the default for 'on', and uses for a flag. The remaining gap is the identity of 'ref', which is left to inference.

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% (only 'on' is documented there), so the description must compensate. It explains 'mine' and 'business' thoroughly, but leaves 'ref' entirely unexplained beyond the implied 'the task'. That is one of two required parameters left undefined, so it only partially closes the gap.

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?

The description opens with a specific verb+resource ('Flag a task, or take a flag off') and immediately distinguishes the two flag modes ('mine' vs 'business'), which is the non-obvious part of this tool. It does not need sibling differentiation since no other flag tool exists among the siblings, but it also never states that 'ref' identifies the task to flag.

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?

It gives explicit conditions for choosing each mode: 'mine' works on any board and needs only visibility, while 'business' needs the 'Flag for everyone' permission and is refused on a personal board. It also frames intent ('look at this') and points to the note/plan/comments for rationale. No real exclusion of the tool itself, but the enum routing guidance is strong.

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

All fenbs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?