Skip to main content
Glama

reject

Mark a strategy position as not held and require a note explaining the rationale.

Instructions

Reject a position: I do not hold this. A reason is required.

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": {
      "position_id": "<position_id>",
      "note": "<note>"
    },
    "name": "reject"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
position_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that a reason is required (which the schema's required list already shows) but says nothing about whether rejection is reversible, whether it overwrites an existing adopt, auth requirements, or what the call returns.

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?

Two short sentences, front-loaded with the action and its semantic gloss. No filler, though the second sentence largely restates the schema's required constraint rather than adding new information.

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

Completeness2/5

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

An output schema exists, so return values need no explanation. For a mutation tool with zero annotation coverage and zero parameter documentation, however, the description is too thin: it omits reversibility, side effects on other stances, and any detail about the position_id argument.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it only does so for note by framing it as the required reason for rejection. position_id remains unexplained — no indication of where the ID comes from or whether it must reference an existing/adopted position.

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?

"Reject a position" gives a specific verb and resource, and the gloss "I do not hold this" disambiguates the sense of rejection from deleting or ignoring the position. It contrasts implicitly with siblings like add and adopt, though it never names them.

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 phrase "I do not hold this" implies the situation in which the tool applies (the caller does not hold the position), which is useful implied guidance. There is no explicit when-not guidance, no stated alternatives such as adopt, and no indication of what happens if the position was already adopted.

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