Skip to main content
Glama

searchnapply

This connector has been deprecated

Replaced by searchnapply.

Deprecated.

Show a monitor and what it collected

monitor_get
Read-onlyIdempotent

Purpose: Show one monitor with its counts and a page of the postings it collected; a posting can be old while still hiring. When: The user asks what a monitor found. monitor_review_widget_render shows its newest postings as a list, and job_postings_search_widget_render shows search postings instead. Cost: About 3440 tokens for 20 postings.

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": {
      "page": 1,
      "state": "new",
      "monitorId": 12
    },
    "name": "monitor_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe 1-based page number.
stateNoWhich of the monitor's postings to show; default is the ones not yet applied to or skipped.
monitorIdYesThe monitor id from monitor_list.

Output Schema

NameRequiredDescriptionDefault
pageYesThe 1-based page returned.
stateYesThe state the postings below are in.
totalYesHow many postings the monitor holds in this state.
monitorYesThe monitor as saved.
postingsYesThe postings of this page, most recently collected first.
totalPagesYesHow many pages this state fills.
totalIsCappedYesTrue when the count stopped at its cap and more postings are in this state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / state / description
      Previous value: -"Which of the monitor's postings to show; leave it out for the ones the user has not applied to or skipped yet."New value: +"Which of the monitor's postings to show; default is the ones not yet applied to or skipped."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile needs no restating. The description adds behavior annotations do not cover: an explicit cost budget (~3440 tokens for 20 postings) and the freshness caveat that 'a posting can be old while still hiring', which prevents the agent from discarding stale-looking results. It stops short of describing count semantics or how totals relate to paging.

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 clauses (Purpose / When / Cost) are front-loaded, each carrying distinct information with no repetition of the title or schema. Nothing could be cut without losing routing or cost signal.

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 present, return values need no explanation, and all three parameters are documented in the schema. The description supplies the missing decision-layer information: which sibling to use and the token cost. Only minor gaps remain, such as the relationship between the reported counts and the paged results.

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%, including the enum values and the default meaning for 'state', so the schema already carries the parameter burden and a 3 is the baseline. The description only implicitly signals pagination ('a page of the postings') and does not add syntax or filtering nuance beyond the schema.

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 uses a concrete verb and resource ('Show one monitor with its counts and a page of the postings it collected') and immediately scopes the output to counts plus a paged list. It distinguishes itself from the two similarly-named render/search siblings by name, so an agent can separate them without opening a schema.

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

Usage Guidelines5/5

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

It gives an explicit trigger ('When: The user asks what a monitor found') and names the alternatives with the condition that selects them: monitor_review_widget_render for a list of newest postings, job_postings_search_widget_render for search postings. When-to-use, when-not-to-use, and routing are all present.

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