Skip to main content
Glama
Sign In

Selenios

by com.selenios.back
OverviewDiscussionsAdmin

Get application form answers

get_application_form_answers
Read-onlyIdempotent

Get the answers a candidate submitted in the application form of one job position: each custom question with its label, type, whether it was required and the candidate's answer, plus the declared expected salary (declared.pretendedSalary) and location when present. When the position asked for salary as a free-text question, the amount is in answers, not in declared. Shows what the candidate actually wrote, independently of the matching score.

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

Input Schema

NameRequiredDescriptionDefault
candidateIdYesThe candidate ID
jobDescriptionIdYesThe job position the application belongs to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the description's job is to add context, which it does: it discloses the returned field set and warns that free-text salary questions land in `answers` rather than `declared`. It does not mention auth requirements or behavior when the candidate has no application form, but it is consistent with the annotations throughout.

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?

Two sentences, front-loaded with the primary action and followed by the return shape and the one non-obvious caveat. No filler, and the salary caveat is placed where an agent parsing output would need it.

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?

There is no output schema, so the description carries the full burden of describing returns, and it does: question label, type, required flag, the candidate's answer, plus declared salary and location when present. For a two-parameter read tool that is everything an agent needs before calling it.

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%, so both parameters are already documented and the baseline is 3. The description reinforces the pairing — one candidate plus one job position identifies a single application — but adds no format, ID-source, or validation meaning beyond what the schema states.

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 states a specific verb and resource ('Get the answers a candidate submitted in the application form') and pins the scope to 'one job position' via the candidate/job pair. The closing clause distinguishes it from the scoring tools in the sibling list ('independently of the matching score'), so an agent can separate it from get_candidate_score_breakdown 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 Guidelines4/5

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

It gives clear context for selection — this returns what the candidate literally wrote, decoupled from match scoring — which implicitly routes score-related questions to the scoring siblings. It stops short of naming an alternative tool explicitly or stating when not to use it, so it falls just below the top band.

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