Skip to main content
Glama
Sign In

Selenios

by com.selenios.back
OverviewDiscussionsAdmin

Check score recalculation

get_job_score_recalculation_state
Read-onlyIdempotent

Check whether a bulk re-score of a job position can run right now. Returns canRecalculate; the reason when it cannot (a run already in progress, the one-per-hour cooldown, criteria unchanged since the last run, or no candidate with an outdated score); the minutes left on the cooldown; how many candidates would be re-scored; and the progress of a run in progress.

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": {
      "jobDescriptionId": "<jobDescriptionId>"
    },
    "name": "get_job_score_recalculation_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobDescriptionIdYesThe job position to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare the safe read profile (readOnly, idempotent, closed-world, non-destructive), and the description goes well beyond them by disclosing the full set of blocking conditions: an in-progress run, a one-per-hour cooldown, unchanged criteria, and no outdated scores. It also flags the cooldown as a rate-limit style constraint, which is exactly the operational context an agent cannot infer from annotations.

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?

A single front-loaded sentence states the check, followed by an enumerated return payload. The list is dense but every item is actionable information, particularly given there is no output schema; the parenthetical of blocking reasons is long but earns its space.

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

Completeness5/5

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

For a one-parameter read tool with complete annotation coverage and no output schema, the description supplies everything needed: what is checked, every reason the check can fail, and the shape of the returned values including cooldown minutes and run progress. Nothing an agent needs in order to call or interpret it is missing.

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?

There is only one parameter, jobDescriptionId, and the schema documentation coverage is 100%, with the schema itself explaining 'The job position to check.' The description adds no format, source, or lookup detail beyond that, so the schema carries the parameter semantics and a baseline 3 applies.

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 opens with a specific verb and resource: 'Check whether a bulk re-score of a job position can run right now.' This is a distinct pre-flight check, clearly separable from the sibling action tool recalculate_job_scores without opening either schema.

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 phrasing 'can run right now' implies this is a pre-condition check to perform before triggering a re-score, but the description never names recalculate_job_scores as the follow-up action or states when not to call it. 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.

All Selenios toolsInspect
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