Skip to main content
Glama

searchnapply

This connector has been deprecated

Replaced by searchnapply.

Deprecated.

Record decisions on monitor postings

monitor_decide
Idempotent

Purpose: Record what the user did with postings a monitor found. When: After the user says what they did with a posting. Cost: About 20 tokens per posting.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "decision": "skipped",
      "monitorId": 12,
      "postingIds": [
        4711,
        4712
      ]
    },
    "name": "monitor_decide"
  }
}

Input Schema

NameRequiredDescriptionDefault
decisionYesWhat the user did: applied to the postings, skipped them, or open to put a decided posting back to undecided.
monitorIdYesThe monitor the postings belong to, from monitor_list or monitor_get.
postingIdsYesIds of the monitor's postings to decide, 1 to 100, from monitor_get.

Output Schema

NameRequiredDescriptionDefault
failedNoIds whose state could not be written just now; present only when some.
notFoundNoIds the monitor does not hold; nothing changed for them; present only when some.
postingsYesEach decided posting with its state; a posting already in that state is listed unchanged.
monitorIdYesThe monitor the postings belong to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / decision / description
      Previous value: -"What the user did: applied to the postings, skipped them, or open to put them back among the postings not applied to or skipped yet."New value: +"What the user did: applied to the postings, skipped them, or open to put a decided posting back to undecided."
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add context. The 'Cost: About 20 tokens per posting' line is a genuinely useful addition absent from structured fields, but it says nothing about what happens to a previously recorded decision or how batching up to 100 postings behaves.

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 labeled lines, front-loaded with purpose, then trigger, then cost. Every sentence carries distinct information and nothing is redundant with the schema.

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?

With an output schema, full parameter documentation, and rich annotations, the description covers everything an agent needs to decide to call it. The only residual gap is how re-deciding an already-decided posting behaves, which is partially implied by the enum's 'open' value.

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 description coverage is 100% and the enum values, id ranges, and 1-100 bounds are all documented in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies.

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 states a specific verb and resource: recording what the user did with postings a monitor found, which matches the title and clearly separates it from read-only siblings like monitor_get and monitor_list. It stops short of naming any sibling or noting that monitor_update edits the monitor itself rather than posting decisions.

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?

The 'When: After the user says what they did with a posting' line gives an explicit trigger condition, which is more than most definitions offer. It provides no exclusion rules or alternatives, so an agent must infer that monitor_review_widget_render is the read/inspection counterpart.

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