Skip to main content
Glama

TrueInterview

Report an application form

report_application
Idempotent

What went into an application form, question by question. Call it with submitted true once the candidate says the application went in, with each field as they filled it, never on a guess: the role is logged as applied in their tracker, answers to questions their records did not cover are kept so the next form asks fewer, and the form's questions (never the answers) are kept so the next candidate applying to this posting gets the full list. With submitted false it only checks answers against their records (every answer that differs comes back in mismatches) and logs nothing. Send each field's label as the form prints it, its type and options when you have them, and the value. Leave out self-identification answers, ID numbers and passwords: a card or government ID number, a password or a token is refused and nothing is saved.

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": {
      "submitted": "<submitted>",
      "fields": "<fields>"
    },
    "name": "report_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
roleNo
fieldsYes
job_idNo
companyNo
job_urlNo
submittedYes
applied_atNoYYYY-MM-DD; today when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Well beyond the annotations, the description discloses the actual side effects: the role is marked applied in the tracker, uncovered answers are retained, and the form's questions (never the answers) are stored for future candidates. It also states refusal behavior precisely — ID numbers, passwords, tokens are rejected and 'nothing is saved' — and explains what the dry-run mode returns ('every answer that differs comes back in mismatches'). These details are consistent with readOnlyHint=false and destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, and no clause is pure filler. However, the second and third sentences are long run-ons stitched together with colons and semicolons, bundling several distinct behaviors into one breath, which makes the write-side effects harder to scan than the dry-run rules.

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

Completeness3/5

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

For a write tool with eight parameters, no output schema, and near-zero schema documentation, the description covers the critical decision points (mode selection, field format, prohibited data) well. It leaves the caller guessing about the identity/location parameters and about what a successful submitted=true response contains, so it is not fully self-sufficient.

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 only 13%, so the description has to carry weight, and it does add real meaning for the nested fields array: send the label as the form prints it, plus type, options and value. But five of the eight top-level parameters (job_id, company, job_url, note, applied_at) receive no explanation at all in either the schema or the description. The gap is partially closed, not fully.

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 opens with a concrete framing — 'What went into an application form, question by question' — which names both the resource (application form fields) and the action (recording them). It clearly separates the two operating modes (submitted true vs false). It does not name a sibling to distinguish itself from, so it stops short of a 5.

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?

Timing is explicit and conditional: call with submitted true 'once the candidate says the application went in' and 'never on a guess', and with submitted false purely to check answers. That is a clear when-to-use and when-not-to-use split. It never routes the agent to an alternative tool (e.g. tracking or answer-updating siblings), which keeps it from a 5.

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